-
Notifications
You must be signed in to change notification settings - Fork 94
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
submitted state lock #291
submitted state lock #291
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.
A question about timeouts for acquiring the lock; also if you include "Closes #203" in the main PR description GitHub will auto-close the issue
Otherwise this looks clean and robust, nice work!
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.
@jakekaplan this LGTM but would you also mind adding a test at the GraphQL layer within tests/graphql/test_states.py
that replicates the API level test at a higher level ?
@cicdw added the graphql test 👍 |
Summary
Adds an in memory in process submitted state lock. Closes #203
Importance
Currently it is possible for multiple agents to pick up the same scheduled flow_run, this enables a buffer so that if multiple agents try to run the same flow_run only one will succeed.
Checklist
This PR:
changes/
directory (if appropriate)