Those are not backend bugs and are not of interest in sentry reports.

It wraps the call to sentry_sdk.capture_exception while filtering out
exception types that should not be reported to sentry.

Before this commit, parsing the test file would just return
`and more plain text` because it is the largest text part.

This uses `message.get_payload()` instead of `message.walk()`, because
`message.walk()` implements a bottom-up DFS; but with no easy way of
propagating information between nodes.

Browsing a snapshot containing only releases was raising such exception
in debug mode as the vault_cooking dict was not correctly initialized.

Render at most 8 ticks for the vertical axis and compute step from
yMax instead of using a hardcoded value.

Filter out the 2014 label rendering on the horizontal axis.

Use new method origin_visit_get_with_statuses from storage interface
returning all visits and their statuses instead of querying latest
status for each visit.

Also bump the maximum number of visits per page from 50 to 1000.

Related to T4090

Previously, the admin-deposit-list view was retrieving all deposits data
using the /1/private/deposits/ swh-deposit endpoint and was filtering
those client side.

That approach was not efficient at all as the number of deposits
increased.

So from now on, swh-web will simply forward the listing requests to
the new /1/private/deposits/datatables/ endpoint of swh-deposit which
will perform the same filtering and pagination operations as before in
an efficient way.

Also remove code that is now dead and ensure deposit private API base
URL can be set in configuration with or without trailing slash.

Related to T3128

Related to T3922

black is considered stable since release 22.1.0 and the version
we are currently using is quite outdated and not compatible with
click 8.1.0, so it is time to bump it to its latest stable release.

Please note that E501 pycodestyle warning related to line length
is replaced by B950 one from flake8-bugbear as recommended by black.
https://black.readthedocs.io/en/stable/the_black_code_style/current_style.html#line-length

Related to T3922

Related to T4125

Updating origin type counters in coverage widget every hour seems
more reasonable that doing it every 5 minutes as the underlying
database requests are pretty costly.

That function is used to dynamically retrieve the list of origin visit
types (git, svn, npm, ...) currently supported by Software Heritage.

That list of visit types is then used to populate the visit type
dropdown in the search form available in the home and search pages
of the web application.

However getting that visit types list is costly as it involves sending
an elasticsearch query through the use of swh-search.

So instead of sending that costly query each time a search form must
be rendered, prefer to cache the visit types list and update it
every 24 hours.

That change significantly speedup the homepage rendering of the
web application.

Add a decorator enabling to put the result of a function call in Django
cache, subsequent calls will then directly return the cached value.

Use that decorator whenever it is possible in swh-web codebase to simplify
the handling of cached values and improve code readability.

The next version of swh-deposit will do this renaming, for consistency with
_admin_deposit_list and the rest of the codebase.

This function uses the html part if no text part is available. If
multiple plain text or html parts are available, it uses the largest
one.

These utilities allow us to generate addresses of the form
`<localpart>+<integer>.<signature>@<domain>`, where the integer is the
primary key of a given object for which we want to track email
exchanges. The signature prevents the addresses from being forged, that
is, the addresses have to be explicitly generated and displayed by the
web app to be discovered.

The counterpart function retrieves all relevant email addresses from the
list of recipients of an email message, and validates the signatures to
recover the integer values that won't have been tampered with.

These new utilities are expected to be used in the views and signal
handlers pertaining to processing of inbound email messages.

pytest-postgresql 3.1.3 and pytest-redis 2.4.0 added support for
pytest >= 7 so we can now drop the pytest pinning.

This reverts commit ea683ca5.

djangorestframework-stubs 1.5.0 has been released, fixing the observed issue.

It prevents infinite reload of web application in browser when overriding
swh-web sources in docker-compose environment and modifying js sources.

This allows calling the function on a single recipient rather than on a
whole message, when one isn't available.

Other modules still need psycopg2 and pytest-postgresql 4 introduced a
hard dependency on psycopg3.

This restriction has only been needed since a recent dependency
upgrade (or maybe a pip upgrade); pip has stopped being able to solve it
itself for some reason.

as a modal

Related to T4078

Prior to this commit, this was done for all deposits but it's only a good fallback for
typed deposit 'code'.

Related to T4123

Some database tests depend on the text returned by the SQL client, which
is localized. Forcing the C locale ensures the text gets output in
English.