-
Notifications
You must be signed in to change notification settings - Fork 30
Implement refresh mechanism for unknown mergeable PRs #247
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
bf1e6d4
to
4f5b820
Compare
@Kobzol could you take a quick look to make sure I'm on the right track on how I've implemented the background processing for the mergeable queue? You can ignore the logic and what actually happens right now since it's very much a WIP, but I want to make sure I'm going about the actual queue task implementation correctly. |
Yeah, I think that's mostly fine. I would use a "native" queue from tokio, rather than implementing it with a Mutex + sleep, that's unnecessary and hacky. Also waiting 10 secs for the item to be processed in tests would be annoying. Also I would split this into multiple PRs:
|
a38daf6
to
1c57795
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!
]) | ||
.await; | ||
|
||
if results.iter().all(|result| result.is_ok()) { |
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're swallowing errors here, we should log them instead. It was pre-existing though, so let's fix it in a separate PR.
Fixes #218
This PR: