fixing bug if task is None#64
Open
jm22dogs wants to merge 5 commits intomaxpareschi:3.14.11-22dogs.developfrom
Open
fixing bug if task is None#64jm22dogs wants to merge 5 commits intomaxpareschi:3.14.11-22dogs.developfrom
jm22dogs wants to merge 5 commits intomaxpareschi:3.14.11-22dogs.developfrom
Conversation
added 5 commits
March 27, 2025 10:13
…hi/OpenPype into upstream_branch_src
…hi/OpenPype into upstream_branch_src
…hi/OpenPype into upstream_branch_src
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Brief description
Task may exist and be None, which raises an exception later when adding task to the env, as envs only accept strings.
Nonetheless task should not be None, I don't get why was None there... It was already None when exporting the _metadata.json