Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): downgrade jsonschema dependency to 4.17 #10

Merged
merged 1 commit into from
Sep 29, 2023

Conversation

agerveshi
Copy link
Contributor

@agerveshi agerveshi commented Sep 28, 2023

What was the problem/requirement? (What/Why)

deadline-cloud is locked to jsonschema-4.17 as it is the last version to support python 3.7. deadline-cloud-for-nuke has a dependency on this repo as well as deadline-cloud, causing conflicting dependencies.

What was the solution? (How)

Downgrade the jsonschema dependency to 4.17 to align with deadline-cloud

What is the impact of this change?

This repo is also locked to jsonschema-4.17 until we can determine a way to mix dependencies used by the adaptor (which can run python 3.9+) vs the child process being run (such as Nuke 13 which is using python 3.7)

How was this change tested?

  • Unit tests pass
  • Submitted a Nuke job, uploading the adaptor wheels.

Was this change documented?

No

Is this a breaking change?

Yes, dependency version is changing.


By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

This maintains compatibility with python 3.7

Signed-off-by: Alex Gerveshi <[email protected]>
@agerveshi agerveshi requested a review from a team as a code owner September 28, 2023 22:29
@agerveshi agerveshi merged commit 39d557c into mainline Sep 29, 2023
5 checks passed
@agerveshi agerveshi deleted the agerveshi/jsonschema branch September 29, 2023 19:41
Honglichenn pushed a commit that referenced this pull request Jan 17, 2024
Problem:
 When running a Session as a different user on posix systems you will
see a benign, but misleading, error message in the log that looks like:
```
rm: cannot remove '/tmp/openjd/session-name': Permission denied
```

This is caused by our two-phase cleanup of the Session working
directory. We start with a cross-user 'rm -rf' to delete everything in
the directory, and then do a same-user recursive delete. So, the working
directory is getting cleaned up but there is this error in logs that is
misleading.

Solution:
 The `rm -rf` just needs to be changed to `rm -rf <dir>/*` from `rm -rf
<dir>`.

Signed-off-by: Daniel Neilson <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants