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.
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
Replace routerify in file transfer server with axum #2461
Replace routerify in file transfer server with axum #2461
Changes from all commits
4051213
46f3573
e5861c0
12cbcf3
a2eaf4d
ca19392
62dd8f5
63f7f9a
8a920e3
09da1df
22995e5
93aa002
d7a9445
1ca42b2
fd5a907
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
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.
note: We need to be careful with including source error message in parent error message.
I think the recommendation is to not include source error messages like this because proper error reporting/diagnostics will themselves call
.source()
to print messages for the entire error chain. However, for code that is not aware of this, and doesn't depend on any error reporting crates, it will most likely just grab outer error message. It depends where the error is used. For the FTS, I think the errors appear only in HTTP responses and logs, but 1) I'm not sure how they are exactly reported by axum 2) it's all internal so it doesn't matter that much.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'm aware, but knew exactly where these error messages were going (which is only when we call
.to_string()
), and I didn't want to have to convert them to something likeanyhow::Error
just to get a backtrace. You're right though, a lot of thin-edge errors are in library code where they're eventually going to becomeanyhow::Error
and in that case it's really annoying (reqwest
is the example of a public crate that does this that springs to mind).