-
Notifications
You must be signed in to change notification settings - Fork 157
Feat; queuing try commits #2197
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
Feat; queuing try commits #2197
Conversation
8da2e96
to
a9325dc
Compare
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.
Thanks! Left a few comments.
backends, | ||
"", | ||
); | ||
conn.insert_benchmark_request(&try_request).await; |
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.
I wonder if we should return an error here, so that we can e.g. tell to the user that a request already exists, so they can't queue another one, otherwise it will be essentially a silent failure. But we can do that in a future PR.
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 I reckon so, happy to do it in a follow up PR
25d0969
to
cc65504
Compare
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.
Thanks! Please add the test with the completed
try build and we're good to go here, I think.
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.
Thanks! Feel free to merge once CI is green.
RUN_CRON
environment variable to a function