Skip to content

Conversation

@lucix-aws
Copy link
Contributor

Closes #2752.

See above issue for context.

@lucix-aws lucix-aws requested a review from a team as a code owner October 29, 2025 17:16
@Madrigal
Copy link
Contributor

The meat of the issue is your comment here #2752 (comment)

Basically we're removing a customization from go v1 that we are not aware is an issue across SDKs. This will fix #2752 since we're removing the custom middleware that is panicking, but it could (maybe, maybe not) have issues of other people having read timeouts as originally reported. Whether that custom middleware is problematic could also be true, but that's not addressed currently.

I agree that just increasing the read timeout because we weren't sure what the issue was is not the right call and we should remove the customization, but this could surface other issues that we should be ready to deal with

@lucix-aws lucix-aws merged commit f3a3b6c into main Oct 29, 2025
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

3 participants