Skip to content

Conversation

@konstin
Copy link
Member

@konstin konstin commented May 23, 2025

Often, HTTP requests don't fail due to server errors, but from spurious network errors such as connection resets. reqwest surfaces these as io::Error, and we have to handle their retrying separately.

Companion PR: LukeMathWalker/wiremock-rs#159

@konstin konstin added internal A refactor or improvement that is not user-facing network Network connectivity e.g. proxies, DNS, and SSL labels May 23, 2025
@konstin konstin force-pushed the konsti/basic-retry-tests branch from 93bbfd1 to 0309430 Compare May 30, 2025 10:18
@konstin konstin force-pushed the konsti/advanced-retry-tests branch from ce49c26 to 4802438 Compare May 30, 2025 10:18
@konstin konstin requested a review from jtfmumm May 30, 2025 10:18
@jtfmumm
Copy link
Contributor

jtfmumm commented Jun 9, 2025

respond_with_err is very useful. Thanks for adding that!

Cargo.toml Outdated
windows-result = { version = "0.3.0" }
windows-sys = { version = "0.59.0", features = ["Win32_Foundation", "Win32_Security", "Win32_Storage_FileSystem", "Win32_System_Ioctl", "Win32_System_IO", "Win32_System_Registry"] }
wiremock = { version = "0.6.2" }
wiremock = { git = "https://github.com/konstin/wiremock-rs", rev = "131ad0a3e7a247c867fc290319047fc086995271" }
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are you waiting to merge until this is accepted upstream?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If not, can you add a comment explaining the respond_with_err change we're using?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since upstream is not responding, I'll fork into the astral org and tag the commit instead.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated to out fork

Base automatically changed from konsti/basic-retry-tests to main June 10, 2025 10:00
Often, HTTP requests don't fail due to server errors, but from spurious network errors such as connection resets. reqwest surfaces these as `io::Error`, and we have to handle their retrying separately.
@konstin konstin enabled auto-merge (squash) June 13, 2025 09:48
@konstin konstin merged commit e10881d into main Jun 13, 2025
107 checks passed
@konstin konstin deleted the konsti/advanced-retry-tests branch June 13, 2025 09:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

internal A refactor or improvement that is not user-facing network Network connectivity e.g. proxies, DNS, and SSL

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants