Our internal e2e tests are failing due to random network issues with S3. Therefore, we have decided to extend the retry mechanism to handle exceptions, rather than relying only on HTTP status codes
Remaining Tasks
Related PRs in other projects (PASQAL developers only)
Additional merge criteria
Breaking changes
Checklist
[x] The title of the PR follows the right format: [{Label}] {Short Message}. Label examples: IMPROVEMENT, FIX, REFACTORING... Short message is about what your PR changes.
Versioning (PASQAL developers only)
[ ] Update the version of pasqal-cloud in _version.py following the changes in your PR and by using semantic versioning.
Documentation
[ ] Update CHANGELOG.md with a description explaining briefly the changes to the users.
Tests
[ ] Unit tests have been added or adjusted.
[ ] Tests were run locally.
Internal tests pipeline (PASQAL developers only)
[x] Update and run the internal tests while targeting the branch of this PR.
If your PR hasn't changed any functionality, it still needs to be validated against internal tests.
After updating the version (PASQAL developers only)
[ ] Open a PR on the internal tests that updates the version used for the pasqal-cloud backward compatibility tests.
Description
Our internal e2e tests are failing due to random network issues with S3. Therefore, we have decided to extend the retry mechanism to handle exceptions, rather than relying only on HTTP status codes
Remaining Tasks
Related PRs in other projects (PASQAL developers only)
Additional merge criteria
Breaking changes
Checklist
Versioning (PASQAL developers only)
_version.pyfollowing the changes in your PR and by using semantic versioning.Documentation
Tests
Internal tests pipeline (PASQAL developers only)
After updating the version (PASQAL developers only)