Repository navigation
feat(axum): add safe diagnostics and trusted proxy metadata #409
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
Open
ChristianPavilonis
wants to merge
12
commits into
issue-393-buffered-body-limit-spec
from
issue-397-diagnostics-proxy-trust-spec
Open
Changes from all commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
0769cbf
feat(axum): add safe diagnostics and trusted proxy metadata
ChristianPavilonis 61fc149
fix(axum): keep diagnostics behind its native runtime feature
ChristianPavilonis 3cb7f85
Merge verified lower-stack fixture lock
ChristianPavilonis 9fa1666
fix(ci): align diagnostic fixture locks with required dependencies
ChristianPavilonis bee8dc0
Merge corrected lower-stack feature and CI contracts
ChristianPavilonis 3b52b80
fix(axum): separate trusted ingress from retired proxy transport
ChristianPavilonis ef42131
Merge managed demo logging regression alignment
ChristianPavilonis 5bbff2b
Merge native-only scaffold correction into diagnostics stack
ChristianPavilonis 027e161
Prepare authenticated head facts before stripping forwarded fields
ChristianPavilonis 3708ffa
Carry prepared-router installation through the review stack
ChristianPavilonis daae624
Merge current parent repairs into PR 409
ChristianPavilonis 31f46bd
Retain callback-scope fixture repair in PR 409
ChristianPavilonis File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
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.
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.
🤔 New exact pins downgrade the app-demo lock and pull in a second wasm-tools tree
getrandom = "=0.4.2"(andipnet = "=2.12.0"at line 74) are new in this PR; the PR body calls them "existing exact workspace requirements". Because app-demo resolves these through the path dependency,examples/app-demo/Cargo.lockis forced from getrandom 0.4.3 → 0.4.2 and ipnet 2.12.2 → 2.12.0. getrandom 0.4.2 depends onwasip2+wasip3 0.4.0+wasi-0.3.0-rc-2026-01-06, which drags back wit-bindgen 0.51, wasm-encoder/wasmparser/wit-parser/wit-component/wasm-metadata 0.244, prettyplease 0.2.37, hashbrown 0.15.5 and foldhash 0.1.5. That is most of the ~218-line app-demo lock diff. The pin also blocks the root from moving to 0.4.3, which drops the wasip3 RC dependency.The plan (line 113) specifies caret
"0.4.2"/"2.12", and plan line 375 says "No package version changed"; neither matches.Suggestion: use caret requirements (or pin
=0.4.3/=2.12.2and update the root lock), then regenerate the app-demo lock so it only gains the two new edges.