As a compromise, we could accept this trailing slash, but show a warning on the interface and/or codify in the SWHID specification an exhaustive list of "fixes" that user interfaces can/should do.

There are already many URLs in the open

There are already many URLs in the open, so even if we remove the trailing slash now, that does not solve the problem.

What about removing the trailing / from generated URLs like this one instead?

great news!

I finally found why the graphs looks weird : https://forge.softwareheritage.org/source/swh-web/browse/master/swh/web/misc/urls.py$31
With a dirty patch on the server, it's way better:

\o/

The pipeline is deployed in staging.
It's working but it seems the graphs need some initial values in staging to make the rendering correctly:

It has been deployed to production, closing this.

This is now deployed to production.

Operationally, there's two axes we can play with:

Hey, can I take this task up next?

Great!

Thanks @faux, it will be deployed with next swh-web release.

@ardumont we briefly discussed this a while ago with @olasd. I think the proposed
solution was indeed to have a separate queue (and workers) for "save code now"
request, but not necessarily one separate queue per loader,

@ardumont we briefly discussed this a while ago with @olasd. I think the proposed solution was indeed to have a separate queue (and workers) for "save code now" request, but not necessarily one separate queue per loader, because the current priority system wasn't considered to be "fast enough". Maybe we can discuss this briefly with him and synthesize here what you come up with?

We already have a priority queue system in place in the scheduler. And for example, the
archive schedules save code now requests with a priority high [1]

Ok cool.

so for a user having an id like this in the tooltip would feel like an arbitrary string

I had one doubt regarding this, so if the target_type is content then the target would be the content_id, right? But the ids are like this "8e5adfbd7e605bda9c5e96c10e015b3dc0df688e" so for a user having an id like this in the tooltip would feel like an arbitrary string.

Hmmm it's not exactly an alias. <release_name> is actually a reference that can point to a branch :|

release: "The release <release_name> is an alias for release <target_release_id>"

Cool, makes sense. Will work on it and create a diff.

I think label and commit picto dont make sense.

Hi, I would like to take up this task. What should the tooltips be, to me also I think label and commit picto dont make sense.