Feature/3830 handle read timeout error not serializable

[amdomanska]

Make sure that nonserializable error are handled correctly

Please don't delete any sections when completing this PR template; instead enter N/A for checkboxes or sections which are not applicable, unless otherwise stated below

See #3830

Describe the scope/purpose of the PR here in as much detail as you like

Categorisation

This PR...

• [ ] has scripts to run
• [ ] has migrations to run
• [ ] adds new infrastructure
• [ ] changes the CI pipeline
• [x] affects the public site
• [ ] affects the editorial area
• [ ] affects the publisher area
• [ ] affects the monitoring

Basic PR Checklist

Instructions for developers:

• For each checklist item, if it is N/A to your PR check the N/A box
• For each item that you have done and confirmed for yourself, check Developer box (including if you have checked the N/A box)

Instructions for reviewers:

• For each checklist item that has been confirmed by the Developer, check the Reviewer box if you agree
• For multiple reviewers, feel free to add your own checkbox with your github username next to it if that helps with review tracking

Code Style

• No deprecated methods are used

  • [ ] N/A
  • [x] Developer
  • [ ] Reviewer

• No magic strings/numbers - all strings are in constants or messages files

  • [x] N/A
  • [ ] Developer
  • [ ] Reviewer

• ES queries are wrapped in a Query object rather than inlined in the code

  • [x] N/A
  • [ ] Developer
  • [ ] Reviewer

• Where possible our common library functions have been used (e.g. dates manipulated via dates)

  • [x] N/A
  • [ ] Developer
  • [ ] Reviewer

• Cleaned up commented out code, etc

  • [ ] N/A
  • [x] Developer
  • [ ] Reviewer

• Urls are constructed with url_for not hard-coded

  • [x] N/A
  • [ ] Developer
  • [ ] Reviewer

    Testing

• Unit tests have been added/modified

  • [x] N/A
  • [ ] Developer
  • [ ] Reviewer

• Functional tests have been added/modified

  • [x] N/A
  • [ ] Developer
  • [ ] Reviewer

• Code has been run manually in development, and functional tests followed locally

  • [ ] N/A
  • [x] Developer
  • [ ] Reviewer

• Have CSS/style changes been implemented? If they are of a global scope (e.g. on base HTML elements) have the downstream impacts of the change in other areas of the system been considered?

  • [x] N/A
  • [ ] Developer
  • [ ] Reviewer

Documentation

• FeatureMap annotations have been added

  • [x] N/A
  • [ ] Developer
  • [ ] Reviewer

• Documentation updates - if needed - have been identified and prepared for inclusion into main documentation (e.g. added and highlighted/commented as appropriate to this PR)

  • [x] N/A
  • [ ] Developer
  • [ ] Reviewer

• Core model documentation has been added to if needed: https://docs.google.com/spreadsheets/d/1lun2S9vwGbyfy3WjIjgXBm05D-3wWDZ4bp8xiIYfImM/edit

  • [x] N/A
  • [ ] Developer
  • [ ] Reviewer

• Events and consumers documentation has been added if needed: https://docs.google.com/spreadsheets/d/1oIeG5vg-blm2MZCE-7YhwulUlSz6TOUeY8jAftdP9JE/edit

  • [x] N/A
  • [ ] Developer
  • [ ] Reviewer

• The docs for this branch have been generated and pushed to the doc site (see docs/README.md for details)

  • [x] N/A
  • [ ] Developer
  • [ ] Reviewer

Release Readiness

• If needed, migration has been created and tested locally

  • [x] N/A
  • [ ] Developer
  • [ ] Reviewer

• Release sheet has been created, and completed as far as is possible https://docs.google.com/spreadsheets/d/1Bqx23J1MwXzjrmAygbqlU3YHxN1Wf7zkkRv14eTVLZQ/edit

  • [x] N/A
  • [ ] Developer
  • [ ] Reviewer

• There has been a recent merge up from develop (or other base branch). List the dates of the merges up from develop below 6/5/24

Testing

List the Functional Tests that must be run to confirm this feature

N/A

Deployment

What deployment considerations are there? (delete any sections you don't need)

Configuration changes

What configuration changes are included in this PR, and do we need to set specific values for production

Scripts

What scripts need to be run from the PR (e.g. if this is a report generating feature), and when (once, regularly, etc).

Migrations

What migrations need to be run to deploy this

Monitoring

What additional monitoring is required of the application as a result of this feature

New Infrastructure

What new infrastructure does this PR require (e.g. new services that need to run on the back-end).

Continuous Integration

What CI changes are required for this

[amdomanska]

I couldn't reproduce this specific error locally.

Currently the raised exception is tested for the specific condition that requires the 3rd attribute of that exception to be serializable. If the condition is not met, the original exception is raised.

In my PR I added the check to see if said attribute is serializable. If it isn't I skip the check and raise the original exception.

I tested the code by raising the appropriate exception manually.

Please let me know if this approach is not correct.