-
Notifications
You must be signed in to change notification settings - Fork 4
ENG-1634 Re-sync nodes if needed at the time the users publish the node #951
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
Merged
maparent
merged 9 commits into
main
from
eng-1634-re-sync-nodes-if-needed-at-the-time-the-users-publish-the
Apr 14, 2026
+121
−68
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
d8578b2
Do a sync on publish
maparent 3fec3af
break recursion
maparent 801c1f4
isolate asset syncing, to avoid syncing twice
maparent 6f9b189
nit: remove node ref in commented code
maparent 9ca0b9c
lint
maparent 4027e1f
devin suggestion: fail on a per-node basis
maparent f9b90f3
eliminate republish flag
maparent 660ccb3
Notify user of sync failure
maparent c1440af
forgot a return value type
maparent 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
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
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
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
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.
Error is silently swallowed with no logging or user notification. The commented-out error message also references
nodewhich doesn't exist in this scope (should be referencing individual nodes from the loop insyncPublishedNodesAssets). This means:Fix: Either properly log the error or remove the try-catch to let errors propagate:
Spotted by Graphite

Is this helpful? React 👍 or 👎 to let us know.
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.
We are indeed swallowing errors silently in the plugin. @trangdoan982 Do you think this one is worth a Notice?
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.
yeah maybe we show them a Notice and ask them to retry?
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.
Added a notice. Not sure we should ask them to retry, unless we have a way to detect multiple failures?