-
Notifications
You must be signed in to change notification settings - Fork 40
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
update to Dropshot 0.13.0 (minimum changes) #7050
Conversation
@@ -89,6 +89,7 @@ impl<'a> RequestBuilder<'a> { | |||
body: dropshot::Body::empty(), | |||
expected_status: None, | |||
allowed_headers: Some(vec![ | |||
http::header::CONNECTION, |
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.
This curious change appears to be required due to this change in hyper v1.5. Without this fix, I found an update test failed, reporting that it expected a 500. In fact it did get a 500, but it failed the validation we do on all client responses that only these allowed headers were present. It failed that validation because there was a connection
header present.
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.
interesting
…dap/drafts/dropshot-update
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.
ship it
@@ -89,6 +89,7 @@ impl<'a> RequestBuilder<'a> { | |||
body: dropshot::Body::empty(), | |||
expected_status: None, | |||
allowed_headers: Some(vec![ | |||
http::header::CONNECTION, |
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.
interesting
@@ -7,7 +7,7 @@ | |||
"url": "https://oxide.computer", | |||
"email": "[email protected]" | |||
}, | |||
"version": "20241204.0" | |||
"version": "20241204.0.0" |
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 hadn't considered this consequence. I can't see any problems with it; this version string does appear in CLI/SDK stuff...
This PR implements the minimum changes to update Dropshot to the newly-released 0.13.0. For more on this, see: https://github.com/oxidecomputer/dropshot/blob/main/CHANGELOG.adoc#breaking-changes
After this one, I will go back to #6730 to update Omicron to use the new builder interface that's in the latest release.
(I initially created this PR as a test-build of Omicron against Dropshot 0.13.0. See oxidecomputer/dropshot#1115.)