This repository has been archived by the owner on Sep 20, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 128
Context Validation Repair Action enhancements #6207
Closed
bradenjennings
wants to merge
12
commits into
develop
from
enhancement/OP-7955_Context_Validation_Repair_Action_enhancements
Closed
Changes from 1 commit
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
c9e5224
enhancement/OP-7955_Context_Validation_Repair_Action_enhancements
d96692b
enhancement/OP-7955_Context_Validation_Repair_Action_enhancements
1992c1d
enhancement/OP-7955_Context_Validation_Repair_Action_enhancements
c9ddc13
enhancement/OP-7955_Context_Validation_Repair_Action_enhancements
ecde135
enhancement/OP-7955_Context_Validation_Repair_Action_enhancements
f080dc9
enhancement/OP-7955_Context_Validation_Repair_Action_enhancements
ffc4300
enhancement/OP-7955_Context_Validation_Repair_Action_enhancements
514c956
enhancement/OP-7955_Context_Validation_Repair_Action_enhancements
cc491a5
enhancement/OP-7955_Context_Validation_Repair_Action_enhancements
1a8fcc6
enhancement/OP-7955_Context_Validation_Repair_Action_enhancements
d1db83b
enhancement/OP-7955_Context_Validation_Repair_Action_enhancements
fa58657
Merge branch 'develop' into enhancement/OP-7955_Context_Validation_Re…
antirotor File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The validator should not be querying this data - right? This should've been readily collected in the Collectors.
Doing this per instance like this I'm pretty sure will be very slow. This is much better batch collected in a Collector.
Side note: wasn't aware Ayon had frame data per task instead of per folder.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@BigRoy so would you recommended adding a "CollectTaskEntity" to the Maya host collectors.
I want to store the task doc attributes for later query in validators.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup, task entity collecting would make sense. It's happening already for
projectEntity
andassetEntity
or alike on bothcontext
andinstance
(note that Instance MAY target a different asset than current context and thus might need a validation against that instead of the context).I'd look up which collector is currently storing
projectEntity
andassetEntity
which I think it does in a bulk query from aContextPlugin
and add the data collection fortaskEntity
there as well (iftask
is set on the instance/context, etc.)@iLLiCiTiT thoughts?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I found where project and asset entity are added to context, this is in
I now prepare and cache the "taskEntity"here.
https://github.com/ynput/OpenPype/pull/6207/files#diff-65495e9f1aba1baa5c1f7517ad5f56e80c42990db087260f8ee4a5eee6edb1c1R17
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@BigRoy it seems get_task_by_name is only in ayon_api.
I guess I need to make OpenPype legacy work without ayon in the mix?
In which case I should test if AYON_SERVER_ENABLED, and then only do the query in ayon.
I assume there was no API for this in legacy OpenPype
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it would be easier if I don't have to back support OpenPype without AYON.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup, there's no equivalent "task" data in OpenPype as far as I know.
Since this is in the OpenPype repo I'm pretty sure you'll still need to maintain backwards compatibility. But might be a better question forwarded to @mkolar or @iLLiCiTiT