Retry on HTTP 522 Connection timed out

[findepi]

This is supposed to be CloudFlare specific 522 Connection timed out HTTP error code.

Description:

Extend the list of HTTP error codes on which network communication is retried, by adding 522 to ot.

Related issue:

• meant to fix setup-java sometimes fails with Trying to resolve the latest version from remote Error: error code: 522 #963

Check list:

• Mark if documentation changes are required.
• Mark if tests were added or updated to cover the changes.

[Copilot]

Pull request overview

This PR extends the retry mechanism for network errors by adding CloudFlare's HTTP 522 (Connection timed out) status code to the list of retryable error codes.

• Adds HTTP 522 to the array of retryable HTTP status codes alongside existing codes (429, 502, 503, 504)

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review for a chance to win a $100 gift card. Take the survey.

[Copilot]

The addition of HTTP 522 to the retryable status codes is appropriate, but there's no test coverage for the retry logic with HTTP status codes. Consider adding tests to verify that HTTP 522 (and other retryable status codes like 502, 503, 504) trigger the retry mechanism correctly. This would help prevent regressions and document the expected behavior.

[findepi]

Is there existing test that i should extend that covers existing retries?

[priyagupta108]

Hello @findepi 👋,
Thank you for your pull request. Could you please run the npm run build command to regenerate dist directory. If you need any help feel free to ping us.

[findepi]

@priyagupta108 i run npm install and npm run build.
This resulted in dist/ changes as expected, but also modified package-lock.json. Should i revert changes in package-lock.json?