Fix bug with running graphs in temporal workflows #3459
Closed
+496
−27
Conversation
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
dmontagu
force-pushed
the
temporal-graph-example
branch
from
594d12a to
7b10ea7
Compare
Contributor
Author
|
Closing in favor of #3460 which doesn't add the "dangling" example |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Graphs are using
uuid.uuid4()currently which is too random for temporal.This PR changes things so we use a deterministic approach to generating task and node-run IDs, and eliminates the (essentially unused) graph run ID.
This PR also adds an example of a multi-agent graph for research that runs using temporal.