Chore: Extend the live service utility for handling 503 errors

[stumpylog]

Proposed change

I'd written two of these utilities to handle HTTP errors when using Gotenberg/Tika in the CI test runs. This combines them into a single place for usage. It will probably fail right away, but it seemed to be more stable in my numerous re-runs.

The best change is probably the skipping if the calls all failed with HTTP 503 errors. We don't really care if the server died in our tests.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Other (please explain): - Code cleanup

Checklist:

• I have read & agree with the contributing guidelines.
• If applicable, I have included testing coverage for new code in this PR, for backend and / or front-end changes.
• If applicable, I have tested my code for new features & regressions on both mobile & desktop devices, using the latest version of major browsers.
• If applicable, I have checked that all tests pass, see documentation.
• I have run all pre-commit hooks, see documentation.
• I have made corresponding changes to the documentation as needed.
• I have checked my modifications for any breaking changes.

[shamoon]

Worth a shot! This is the last bugaboo in our ci but yea seems random and is rarely relevant.

[shamoon]

I dont get why this didnt work?

[stumpylog]

I do. The errors are chained, so the actual raised error is a ParseError from an httpx.xyzError. I'll need to do some tweaking

[stumpylog]

8 runs without a failure. Naturally, it will fail immediately in dev. In some hacked up testing, it does properly handle a ParseError from an HTTPStatusError and the status code skipping of a test.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion or issue for related concerns.