consider retrying 500 errors on poetry install

[novas0x2a]

• I have searched the issues of this repo and believe that this is not a duplicate.
• I have searched the FAQ and general documentation and believe that my question is not already covered.

Feature Request

It's certainly perfectly normal to avoid retrying http 500s, but on the modern internet 500s tend to be extremely transient, so I was wondering if you'd consider permitting 500s to retry. It looks like, currently, the uploader retries 500--503, and the authenticator retries 502--504. Was this difference intentional?

There is actually a PR that aligns them, though it hasn't seen much attention, I think: #7072

[dimbleby]

this is a duplicate of #7072, as you have pointed out yourself.

(I would agree that the backlog of PRs not getting attention is a sad thing: but I don't expect that duplicating PRs with issues will help)

[novas0x2a]

Yeah, sorry, a lot of projects won't look at PRs unless there's an associated issue, wasn't sure if that was the case here.

[nejch]

Hey folks, I'm the author of that PR. I'll try to get to a windows machine so I can reproduce the Windows CI failures (or maybe rebasing will help already).

Maybe once the CI is green, it'll get more attention from maintainers. I'd be keen to get that merged of course as well :)

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.