-
Notifications
You must be signed in to change notification settings - Fork 16
Prep for 1.0 alpha, adapted to runtime changes in main #25
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
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.
Converting from Int64 to Int can trap. We should throw an error instead.
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 matching the AHC response header parsing behavior: https://github.com/swift-server/async-http-client/blob/c70e0856797ef826ff13627790241011f831975f/Sources/AsyncHTTPClient/AsyncAwait/HTTPClientResponse.swift#L135
If AHC changes to throwing errors, we should update the transport too.
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.
Yes but no 😄 The code you linked is about parsing the content-length header and a couple lines below you are doing it like AHC. However, we are not looking at the conten-length parsing code right now. This is converting the user defined known size of the request body from an Int64 to an Int which AHC doesn't do at all right now.
Motivation
On main, the HTTPBody length type changed from Int to Int64.
Modifications
Adapted the transport with this change.
Result
Repo builds again when using the latest runtime.
Test Plan
Adapted tests.