-
Notifications
You must be signed in to change notification settings - Fork 668
8888: DYN-9176 : optimize graph execution for dna #16374
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
Conversation
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.
See the ticket for this pull request: https://jira.autodesk.com/browse/DYN-9176
|
Is there a different ticket number? This seems to point to something else |
johnpierson
left a comment
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.
lgtm, just if we can reference the correct jira ticket or make one if needed
Ok, I created one. I'm usually using magical numbers 7777,8888,9999 when a Jira is not available/created yet :). |
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.
See the ticket for this pull request: https://jira.autodesk.com/browse/DYN-8888
Purpose
Avoid marking the graph with unsaved changes while in transient state.
Avoid requesting a graph run while in transient state.
The graph will be marked with unsaved changes only when confirming a cluster ( or a single node ) and a single run will be performed in both automatic and manual mode.
Declarations
Check these if you believe they are true
*.resxfilesRelease Notes
Optimize graph execution in the context of node autocomplete new experience.
Reviewers
@DynamoDS/synapse