In the save code now administation page, display a new modal when
rejecting a save request enabling to add a rejection note through
the use of a text area.

Default behavior is to enter a custom note but a couple of prefilled
rejection notes can be selected for the following cases:

  - the origin URL is not a repository link
  - the visit type for the origin URL is not valid
  - the origin URL cannot be found

Related to T3256
Related to T3257

File has been renamed in a recent commit.

Some tests input data returned by swh-web fixtures are sampled from
filtered objects stored in a static test archive.

In order to reproduce any failing test with the same fixture data:

- add a new autouse function scope fixture setting the random seed
  to current time before each test execution and putting that seed
  in cache

- implement custom pytest reporting which adds a new section detailing
  the random seeds used for each failing test and the pytests commands
  to reproduce the failures

- add a new pytest option --swh-web-random-seed enabling to explicitly
  specify the random seed that will be used to run the tests

Some tests input data returned by fixtures are sampled from filtered
objects stored in a static test archive.

In order to avoid repeating the same filtering operations multiple
times, put these filtered data in cache.

Related to T3658

As this is done through a decorator to replace a variable in a docstring,
it has the side effect to call swh-scheduler API when importing the module.

This is not required when running tests so do not fetch that list of
visit types in that case.

Apart a couple strategies who are still used in some swh-web test inputs,
turn the remaining ones into pytest fixtures.

Closes T3603

Related to T3603

Related to T3603

Related to T3603

Related to T3603

Related to T3603

Using such hypothesis strategies have several drawbacks so let's
turn them into pytest fixtures as it feels a better way to do so.

Related to T3603

Add an extra parameter called directory_url in the snapshot_context.
To fix the missing URL to the code (directory) view in case the
snapshot is missing an origin context.

Fixes T3644

swh.model.swhids module should be used instead from now on.

Also remove references to *_identifier functions in documentation.

Users with the "swh.web.api.save_origin" permission:

  - will not be rate limited on the /api/1/origin/save/ endpoint

  - will have their save requests immediately accepted

It ensures it will be ignored by git and will not be committed accidentally.

Ensure to restore origin visits visualization state (aka visits filtering)
when reloading page.

Handle "created" and "not_found" statuses in origin visits visualization.

Put visit statuses colors in a dedicated file in order to share them
between modules.

The generation of raw extrinsic metdata links only available for staff users
at the moment was not covered by tests and some bugs slip through.

That commit fixes those errors and improve related tests implementation.

Optional rejection note for a save request will be send in POST request
body of the "admin-origin-save-request-reject" django admin view.

Related to T3256

It will enable to store a swh-web admin redacted note related to
the save request, for instance the reason of rejection or explain
why a submitted save request failed.

Related to T3256

When logged in as a staff user, a new checkbox will be displayed
enabling to search origins with the swh-search query language.

Remove not needed configuration entry.

Open query language documentation in a new browser tab.

Related to T2254

Added reset_sequence=True in the db fixture
Pinned psycopg2 to < 2.9 (To fix UTC related assertion error)
Changed conftest to use sqlite3 for frontend tests

Related to T3424

This produces a lot of noise when running tests and capturing
output so silent those debug logs.

The Origin model from swh-model now includes the origin id leading to
errors when serializing to JSON.

So filter out that field from the conversion to remove thsoe errors
plus it should not be leaked to end users in Web API responses.

This should allow to write your config file like:

web.yaml:

  production_db:
    name: postgresql:///?service=swh-web

thus allowing to use pg_services and pgpass to declare postgresl access
configuration.

Might help for containerized execution environment where db
configuration can be dynamic.

vlorentz authored 3 years ago and Antoine Lambert committed 3 years ago

Those should have been replaced since some time now as swh-web
was the latest component to use these constants.

Includes changes from anlambert suggested during code review.