-
-
Notifications
You must be signed in to change notification settings - Fork 681
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
improve error handling in route #1808
Conversation
Hi again and thanks for working on this! Are you interested in expanding this PR a bit and helping us to remove all calls to |
Thanks for your detailed explanation, it's a pleasure to do it |
hi @har7an , could you please review my code again? |
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 for continuing to work on this!
It seems last time I looked over your code I was a bit sloppy, and I want to apologize for that. If you apply the changes below this is good to go.
Edit: And you'll have to rebase your code, I see someone changed route.rs
on main
in the meantime.
2edeeeb
to
86510a3
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.
Well done, thanks for your effort!
let mut retry_queue = vec![]; | ||
let err_context = || format!("failed to handle instruction for client {client_id}"); |
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.
Great, thank you!
Improve error handling in `server/route`.
Replacing
unwrap
inroute.rs
with error propagation.Related to #1753