python-memcached backend has been replaced by pymemcache since django 3.2.

Related to #4734

It also enables to remove the version restriction on psycopg2.

However, upstream django-js-reverse requirement is not compatible
with django 4.x so we have to use a patched version.

Related to #4734

Related to #4734

Related to #4734

Browse views used to render a directory have a path query parameter to
request the display of a sub-path reachable from the directory.

If the path was targeting a file, the views were returning a 404 error
so prefer to redirect to the content view instead.

Related to #4331

Currently when querying the /browse/content/raw endpoint, the Content-Type
header of the HTTP response is set to text/plain when the content is textual
to force browser rendering and to application/octet-stream otherwise to force
file download.

However some image formats can be rendered by browsers and it seems better to
display them instead of offering their downloads, so ensure those will be
rendered by browsers.

img tag was not closed and alt attribute was missing.

Thanks to Baptiste MÉLÈS for reporting that issue.

Jérémy Bobbio (Lunar) authored 2 years ago and Jérémy Bobbio (Lunar) committed 2 years ago

Related to swh/meta#4959

Related to swh/meta#4960

This fixes python 3.7 support due to poetry, a dependency of isort, that
removed support for that Python version in a recent release.

Related to #4728

Update top banner announcing downtime of SWH services from Tuesday
2023-01-24 09:00 to Wednesday 2023-01-25 18:00 UTC+0100.

Related to #4728

It can be useful to follow up on a single Save Code Now request through
the Web API.

To do so, add a new Web API endpoint /api/1/origin/save/(request_id)/
to get info about a request using its unique identifier.

Add request identifier and its info URL in the JSON data returned by the
/api/1/origin/save/(visit_type)/url/(origin_url)/ endpoint and the save
origin webhook ones.

When sending a GET request to /api/1/origin/save/(visit_type)/url/(origin_url)/
endpoint, the SWHID of the resulting snapshot for a save request is now part of
the returned data along with the snapshot URL.

The snapshots associated to the save code now visits for a given origin are
retrieved on demand and then put in cache in the SaveOriginRequest django
model.

metadata_authorities_url field is returned when querying the /api/1/origin*/
endpoints, not the /api/1/origin/visit*/ ones.

Many emails still use non-UTF8 encoding, especially ISO 8601-1;
before this commit they ended up with the Unicode Replacement Character

In order to remove warnings about /apidoc/*.rst files being included
multiple times in toc when building full swh documentation, prefer to
include module indices only when building standalone package documentation.

Related to T4496

As a SWHID with qualifiers might have some percent encoded characters (like ;
which is used as separator between qualifiers) and HTTP servers will unquote
received URL arguments, a SWHID must also be percent encoded when used as an
URL argument.

This prevent HTTP errors when trying to browse such SWHIDs as previously the
unquoting performed by HTTP servers would remove percent encoding of qualifiers
and thus break escaping of ; used ad separation character.

Quoted white spaces might have been automatically unquoted when a
SWHID is passed as URL argument so ensure to quote them back in
get_swhid function.

Django might try to access the file if the value provided to the filename
query parameter of associated views is an absolute path.

In the save code now requests table, add a webhook icon in the Info column
indicating if a request was created from a popular forge webhook receiver.

Related to T4548

It enables to have some statistics in grafana about the number of save code
now requests created from forge webhook receivers.

Related to T4548

It enables to distinguish which requests were created from a forge
webhook receiver and which forge type sent the webhook.

Related to T4548

When requesting a vault cooking creation but there is already a pending one
for the same SWHID, ensure task creation modal is displayed as previously an
error was erroneoulsy reported in the Web UI.

Under the hood, no new cooking task will be created but the pending one will
be displayed in the vault UI. Nevertheless the email possibly submitted by the
user in the modal will be added to the list of emails to notify by the vault
backend.

Related to T4698