Stathi C.

The problem is it modifies our go mod to include a toolchain line with the patch version. This is the only project that currently causes this to occur in our...

> Is the Go version in your `go.mod` older than 1.22.0 ? (note that 1.22 is considered older than 1.22.0) > If so you probably just need to set the...

I am mistaken on the package. It's coming from datadog-agent: https://github.com/DataDog/datadog-agent/blob/main/go.mod#L3 I am curious why you're deadset against doing a find and replace of `go 1.22.0` -> `go 1.22`?

> and 1.22 is considered "older" than 1.22.0 specifying `go 1.22` vs `go 1.22.0` does the following: You MUST be on ANY version of go greater than or equal to...

@pgimalac it's unfortunate you closed this. The purpose of specifying the patch version is if the following is true: - The dependent package cannot support ANY patch rendition of a...

Thanks for confirming it's still active @VojtechVitek. I made a low risk (and backwards compatible) change to handle pre parsed multi value headers. Currently the implementation assumes the header will...

It seems this issue was attempted to be fixed in #7061, however the issue still persists

Docker 4.33 seems to have caused this issue, downgrading to 4.32 fixed it for now. Can you please look into why?

> As discussed in the previous issue, this is not originating from SAM CLI, but it is coming from Docker Desktop. What happens if you try to build with `SAM_BUILD_MODE=debug...

> Just to confirm you are using a Rust lambda function right? > > > Docker 4.33 seems to have caused this issue, downgrading to 4.32 fixed it for now....