Dan Cook
@xlem.net
software dev | 🇨🇦
github.com/dotxlem
github.com/akkoro
github.com/dotxlem
github.com/akkoro
Fixed!
The SDK requires setting a behaviour version for the client, and looking into that more, apparently that configures the HTTP client and TLS stack
I was using latest which is 2025_01_07 ... I reverted to v2024_03_28 and it worked! So something's up with the newer Hyper client in release mode
The SDK requires setting a behaviour version for the client, and looking into that more, apparently that configures the HTTP client and TLS stack
I was using latest which is 2025_01_07 ... I reverted to v2024_03_28 and it worked! So something's up with the newer Hyper client in release mode
June 10, 2025 at 1:03 AM
Fixed!
The SDK requires setting a behaviour version for the client, and looking into that more, apparently that configures the HTTP client and TLS stack
I was using latest which is 2025_01_07 ... I reverted to v2024_03_28 and it worked! So something's up with the newer Hyper client in release mode
The SDK requires setting a behaviour version for the client, and looking into that more, apparently that configures the HTTP client and TLS stack
I was using latest which is 2025_01_07 ... I reverted to v2024_03_28 and it worked! So something's up with the newer Hyper client in release mode
On HeadObject I don't get any error details, but on a PutObject it the error is HttpVersionNotSupported
Against Garage I got something similar, "invalid http version parsed" or something like that
Makes it sound like in release build the client HTTP version doesn't match what the server expects
Against Garage I got something similar, "invalid http version parsed" or something like that
Makes it sound like in release build the client HTTP version doesn't match what the server expects
June 9, 2025 at 11:48 PM
On HeadObject I don't get any error details, but on a PutObject it the error is HttpVersionNotSupported
Against Garage I got something similar, "invalid http version parsed" or something like that
Makes it sound like in release build the client HTTP version doesn't match what the server expects
Against Garage I got something similar, "invalid http version parsed" or something like that
Makes it sound like in release build the client HTTP version doesn't match what the server expects
This feels a little bit like what Amazon tried to do with Alexa Skills back when voice assistants were supposed to be The Next Big Thing
March 11, 2025 at 10:19 PM
This feels a little bit like what Amazon tried to do with Alexa Skills back when voice assistants were supposed to be The Next Big Thing
Reposted by Dan Cook
Most AI related valuations are rooted in a narrative that AI is closer to magic, that only a few magicians can preform, than just another approach to software architecture.
January 27, 2025 at 2:45 PM
Most AI related valuations are rooted in a narrative that AI is closer to magic, that only a few magicians can preform, than just another approach to software architecture.
So now my library appears to be gone, or at least is no longer available to me AND none of my devices will sync with each other even if I wanted to start over (which I absolutely do not)
January 18, 2025 at 12:27 AM
So now my library appears to be gone, or at least is no longer available to me AND none of my devices will sync with each other even if I wanted to start over (which I absolutely do not)
