Bump development tools: mypy, codespell, isort, ...

Move all tools configuration in pyproject.toml.

Remove no longer needed mypy overrides.

The login command could crash if the authentication setup was not
performed so ensure to execute that setup when it is required to
avoid traceback.

Make it in phase with latest UI changes of the cli.

- add installation alternatives (uv and pipx)
- remove the `swh scanner login` section; it's handled by the `swh
  scanner setup`
- add an extra warning for permissions on provenance API.

One cannot use sphinx specific roles when the README.rst content is used
as python package description.

Always handle the asked output format then run the web ui if
the interactive flag is set.

Rename the '--interactive' option flag as '--web-ui/--no-web-ui' and
make it True by default.

Set the default concurrency to 5.

This should probably be better done than modifying global vars in the
`swh.scanner.data`, but it would require significant rework of the code,
which is not due time yet.

The retry have some exponential delay to avoid hammering the server.

This can happens when too many requests accumulate faster then they are
served. Given the current low number of provenance workers, this can
happens from time to time.

The retry have some exponential delay to avoid hammering the server.

This can happens when the provenance API is too slow to reply. This
happens less now but can still occurs. Doing some retry would prevent
an abort of the operation.

It was typically shown as 'Results for .' which is not very helpful by
any mean.

Pierre-Yves David authored 7 months ago and vlorentz committed 7 months ago

The point of that command is to help initial user to setup the scanner.
So it should be promiment in the readme.

Pierre-Yves David authored 7 months ago and vlorentz committed 7 months ago

Traceback are not great. Let us display a proper error.

We need newe version for swh-model and swh-web-client to operate.

We should nudge the user toward SWH instead of crashing with a
traceback.

Not sure why we sometimes get these, but we do.

Some silly error escaped testing.

Apparently, trailing slashes on directory are the scourge of computing
and keep introducing bug in the swh scanner.

This was not a Path, but it was not caught because the calling function
was not typed.

In some case it is just ugly, in some other, it crashed.

Previously, the dashboard was not using prefetched provenance data and
was chocking on the QualifiedSWHIDs provided.

This is now fixed and working.

We had to change the way the javascript we access data, teach json to deal
with the QualifiedSWHID, and make sure the prefetched data are used and
displayed by default.

The API is now online.

Align with swh-web 0.7.0

This is useful when running the scanner on a remote machine.

Some pieces seems more important than other, lets move them up.

The same item will typically be refereced in many location, we should
avoid useless requests that load the server and consume our rate limit
budget.

Using the same WebAPIClient instance is important if we want to respect
rate limiting.

This will guide first time users by providing an overview of the
features, privacy concerns, helping with authentication and
configuration options, as well as giving a few examples of how to scan.

This actually computes the partial matches recursively and makes the
front-end logic simpler, while providing better and more useful
feedback to the user.

As mentioned in a previous commit, this changes the partial match icon
to always be 50% to make it more obvious and more friendly to
colorblind people.

This makes it unambiguous. A future patch will make the partial case
always look at 50%, since that is more obvious and friendlier to
colorblind people.

Before this patch, if you ran `swh scanner scan some-path`, the vcs
machinery would look at the vcs ignores for... your current working
directory and not the one you"re scanning. Oops.