Related to T4057

This fixes an inconsistency when accessing the add-forge-now moderation view as admin
without any moderation permission.

This now consistently let access to moderation to any person who is either staff or with
an add-forge-now moderator role.

This fixes errors when using django 3.2 and thus the packaging
on debian unstable

URLs targeting a django view must have a trailing slash as
django builtin feature APPEND_SLASH is activated by default.

If an URL definition does not have a trailing slash, this
will  result in a 404 error as django will automatically add
a trailing slash if a user forgot to add it and thus the URL
resolving will fail.

This will avoid having to flip it on by default all around.

Related to T4040

This is:
- plainly displaying the text message when a conflict occur.
- parse the json response otherwise when an input failure occurs.
- if the json response parsing fails too, the raw json is displayed as fallback

Related to T4052

My bad, a couple of years ago I deactivated box shadows used by
bootstrap to emphasize selected form elements.

Related to T4060

Related to T4040

Jayesh authored 3 years ago and Antoine R. Dumont committed 3 years ago

To be used by moderators to update the status of a request
Shows details about a request and its history
Cypress tests

Related to T3992
Related to T4003
Related to T4001

This also prevents the server code from being served when the feature flag is off.

Related to T4040

In a future commit, it will be possible to browse from that view to the detailed request
dashboard.

This also reworks the left menu to allow access to staff or people with the add forge
now moderator permission.

Related to T3991

This will allow easier adaptations when adding new views with different permissions.

Jayesh authored 3 years ago and Antoine R. Dumont committed 3 years ago

Added a form to submit an "add forge now" request.
Left menus changed to include "add forge now" page.
Possbility to browse existing requests is added
in a seperate tab in the same view.
Cypress tests

Related to T3998
Related to T3989
Related to T4012
Related to T3988

Antoine Lambert authored 3 years ago and Antoine R. Dumont committed 3 years ago

Merging datatables special processing in /api/1/add-forge/request/list
endpoint implementation was quite disturbing.

So better using a dedicated endpoint for that in a similar manner as
with save code now requests listing.

The endpoint to use with datatables is now the following one:
/add-forge/request/list/datatables.

Related to T3989
Related to T3991

Antoine Lambert authored 3 years ago and Antoine R. Dumont committed 3 years ago

datatables is the javascript library we use on the frontend side to
display interactive tables.

As we use server-side processing, table data must be provided in a
paginated way by an HTTP endpoint.

Response format expected by datatables is different from the one
returned by the Web API endpoint listing add-forge requests.

So adapt the response format of that endpoint when we know the
input request has been sent by datatables.

Related to T3989
Related to T3991

Antoine Lambert authored 3 years ago and Antoine R. Dumont committed 3 years ago

Related to T4030

Antoine Lambert authored 3 years ago and Antoine R. Dumont committed 3 years ago

Related to T4027

Antoine Lambert authored 3 years ago and Antoine R. Dumont committed 3 years ago

Related to T4026

Antoine Lambert authored 3 years ago and Antoine R. Dumont committed 3 years ago

Related to T3990

We get a couple of these every week.

In the Save Code Now Web UI, the two displayed tabs have different URLs
but it was not possible to navigate back and forth between them when
clicking on the "Go back" and "Go forward" browser buttons.

So ensure the correct tab will be active when URL fragment has changed.

Before each test suite, cypress visits the root page to get some
references on javascript objects used in tests.

However the root page requests the costly /coverage endpoint to
render the archive coverage widget.

We do not need that widget to render for cypress tests so better
mocking that request to an empty one to speedup each test suite
startup.

webpack-dev-server watches static files and will reload application in
the browser when one of them is modified.

However, we need to ignore sqlite3 database files used in development
mode as any HTTP request that modifies the database will trigger an
unexpected page reload.

Some cypress tests use input data generated before each test suite.

Some of these data are retrieved by sending HTTP requests to the
Software Heritage Web API, which can take some times, especially
when repeating that processing before each test suite.

So instead of sending those HTTP requests before each test suite,
prefer to do it once and put the test data in global cache. Those
data will then be set to test suite scope through the use of a
custom cypress task.

Each time a swh-web HTML page is loaded, an HTTP request is sent to
https://status.softwareheritage.org for getting the data needed to
display the status widget in the top right of the Web UI.

That request was not globally intercepted by cypress resulting in
making real HTTP requests on the internet while executing tests.
As a consequence, this was slowing down the whole testing process.

So ensure that request is globally intercepted to speedup tests
execution.

On small resolution screens, the sidebar content could not be scrolled
to the last menu entry.

rst_to_html is called by get_readme_to_display, which processes unsafe data;
so it should not allow inclusion of arbitrary files or arbitrary HTML.

This explicits the deposit's type, either 'code' or 'meta'. The uri column is now filled
depending on that type. Mostly, the parsing of the deposit's raw xml content is done to
try and extract that potentially provided information.

If not found, this uses the same heuristics as before (either use the origin_url if
provided or extract the origin out of the swhid_context).

Related to T3680

Closes T3970

It is time to make the guided tour public.

Also remove old help page as its content is now redundant with swh
sphinx documentation. Clicking on the help icon will now launch
the guided tour for all users.

Move workarounds introduced in f7b35626
and 55aa143d from requirements.txt
file to requirements-test.txt as those break debian package installation.

It enables to update origin counters more frequently in the coverage
widget of the production webapp.

Also disable cache use when running swh-web in development or staging
environment to get accurate counters on each homepage refresh.

Add functions to check if we are running a development, staging or
production version of swh-web.

When loading task types are available for these visit types in the
swh deployment environment (currently staging and docker), display
the associated counters in the coverage widget.

Related to T3945

Related to T3835