Drop visit_type label in prometheus gauge.

Fix docstring

Build is green

Build is green

Update: Add label for webhook origin in prometheus gauge

Update: also add column in save_origin_requests table indicating which forge type sent the webhook

one question to team inline.

In D8889#231323, @vlorentz wrote:

In D8889#231299, @anlambert wrote:

And would it make sense to store which webhook was used?

It can be easily guessed from the origin URL so I do not think we should add that info.

How? That works for Bitbucket and GitHub, but you can't tell whether "git.example.org" is Gitlab or Gitea

In D8886#231331, @vlorentz wrote:

@anlambert Looks like you should use a separate logger, so it integrates with the standard logging config, eg.

swh -l DEBUG -l swh.loader.svn.whatever:INFO loader run svn <repo_url>

to have all debug logs except from the swh.loader.svn.whatever logger

@anlambert Looks like you should use a separate logger, so it integrates with the standard logging config, eg.

Build is green

In D8889#231299, @anlambert wrote:

And would it make sense to store which webhook was used?

It can be easily guessed from the origin URL so I do not think we should add that info.

address review comments

In D8889#231299, @anlambert wrote:

What is it going to be used for?

To compute some stats about usage of that feature.

And would it make sense to store which webhook was used?

It can be easily guessed from the origin URL so I do not think we should add that info.

Landed through 23b3255c3cbd3deed8c7865ae1d1ca7045bdd386

Makes sense.

What is it going to be used for?

In D8886#231281, @lunar wrote:

Could you explain why using loglevels would not work? It feels to me they are meant to solve the problem of selecting the appropriate amount of debug messages… Having a separate flag introduce quite some extra noise in the process.

What is it going to be used for?

Could you explain why using loglevels would not work? It feels to me they are meant to solve the problem of selecting the appropriate amount of debug messages… Having a separate flag introduce quite some extra noise in the process.

See D8894 for an alternative implementation.

Build is green

fix setup.py and doc

Build has FAILED

fix tox.ini + remove option to configure graph name

Build has FAILED

• luigi: Simplify compression task

tests will pass when swh-dataset is released

What is it going to be used for?

(I've at least pushed the main branch and relevant tags)

As I've suspected, this is due to the pristine-tar branch having objects that exceed 100MB:

ooh, I should use this on https://docs.softwareheritage.org/devel/swh-graph/grpc-api.html too

We should add some tests so the code doesn't break when we change other stuff. I'll try to do it this week

Build is green

bump schema version and add migration

Fixed and deployed.

In T4657#98361, @lunar wrote:

[...]
@douardda: would you agree?