It has not been executed for years (skipped if nomossa is not installed)
and so is completely broken (and pretty much useless).

Side effect of swh/devel/swh-storage@e0010b7d.

Those should not be displayed when the sidebar is collapsed.

Some README sections were still in markdown format so turn their to rst.

Include the README as a toc in index.

Guillaume Samson authored 1 year ago and Antoine Lambert committed 1 year ago

Related to swh/devel/swh-web#4760

Split the main nav in sidebar into two navs: one for the features menu
and one for the administration one.

Use h6 elements to display the menu headers.

Update aria label for the navs.

Related to #4767.

Change the main header tag from nav to header.

Move the fixed top bar containing external SWH links inside the header tag.

Update position of the corner ribbon displayed for dev and staging version
of the webapp to a lower one due to a z-index issue.

Related to #4767.

Remove duplicated top left logo link.

Add visual clue when a menu item gets keyboard focused.

Ensure menu headers cannot receive keyboard focus.

Related to #4767.

Related to #4767.

Related to #4767.

Related to #4767.

For consistency with other buttons in the group containing it.

The "Save again" button could not be reached by using the keyboard.

Related to #4767.

Fix all accessibility critical errors detected by IBM Equal Access
Toolkit and Axe.

Related to #4767.

This is the first link in each page and is only displayed when it gains
keyboard focus.

It enables for users navigating with keyboard to quickly jump to the main
content of the currently browsed page.

Related to #4767.

Set and update aria-expanded and aria-label attributes to the hambuger
menu button on the top left part of the UI when the sidebar is expanded
or collapsed.

Related to #4767.

Fix all accessibility critical errors detected by IBM Equal Access
Toolkit and Axe.

Related to #4767.

Add cypress-accessiblity-checker and cypress-axe in order to
write accessibility compliance tests with cypress.

Related to #4767.

Convert README from markdown to ReST to make it embeddable in
docs/index.rst

Overflow values were swapped (x instead of y) so set it to auto in
both directions.

Local file references won't work when embedding the README file in the
main sphinx documentation, so use URLs instead to link to requirement
files.

The RateLimit-Reset header was using the `wait()` method from Django
REST Framework. This method computes the suggested time to wait before
the *next* request to avoid hitting the rate limit.

Instead, we use the `duration` (width of the rate limiting bucket) and add
the timestamp of the first known request to it.

This fixes debian package builds of swh-web.

Cypress >= 13.3 blocked the use of sorry-cypress and cypress-cloud in the
cypress binary so we can no longer use these tools to execute parallel
cypress tests on Jenkins.

Fortunately, it exists another tool called cypress-split that can be used
for the same purpose without relying on a tests orchestration server.

So replace the use of cypress-cloud by cypress-split to still benefit of
parallel cypress tests in CI jobs.

Instead of disabling scheduler service when running cypress tests, use
the recently added scheduler backend spawning a temporary postgresql
database.

In order to update the statuses of save code now requests in a push manner
instead of the current pull one, add a new HTTP endpoint to receive webhook
messages about origins being visited by the SWH archive.

When the visit of an origin results from a Save Code Now request, the status
of the request is then updated when receiving webhook messages notifying
the new status of the visit.

Related to swh/meta#4836.

Paul Wise authored 1 year ago and vlorentz committed 1 year ago

There could be non-technical issues with forge archiving, for example
some admins have responded saying they need to obtain export approval.

Fixes: commit 16ba15e5

It enables to cook a git repository for all supported SWH object types:
directory, release, revision and snapshot.

Previously only a revision could be cooked as a git repository through
the Web API.

Some vault cache backends (azure one for instance) can provide a direct
download link for a cooked bundle. In that case, redirect requests to
the /api/1/vault/(bundle_type)/(swhid)/raw/ to such links in order to
offer efficient downloads and avoid connection errors when dealing with
large bundles.

Related to swh/devel/swh-vault#885.