-
Notifications
You must be signed in to change notification settings - Fork 202
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
MAYA-127478 fix bulk save of root layer filename #2864
Merged
Merged
Changes from all commits
Commits
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
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.
By doing this pull here does it cause any notifications to be sent and could that potentially mess up the clients since we've only done a partial save?
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.
At the point this is called, we are in a pre-save callback AFAIK, so there should be no issue. The "partial" of the comment is in reference to the fact not all layers may have been saved and we are about to save the layers that have not been saved by that partial operation.
OTOH, if the partial save saved only a subset of a complex hierarchy of layers, and the subsequent saving of the remaining layer change their name, they, yes we could be inconsistent in theory. But this was always the case, this PR does not change this nor fix this.
That is, if a stage has the layer hierarchy:
And the partial save only saved 'B' and the the fallback save saves A and C but changes C filenames for any reason, then the sub-layer reference in B won't be the one saved. There is not much we can do about it, but fortunately, this never happens in practice. It may be feasible to artificially trigger this bad behavior in head-less Maya by creating such a hierarchy and writing a batch save delegate that only saves B, but that would be stretching it...