• docker doc: add --publish to the run invocation

• docker doc: drop the list of files generated by Setup class

• docker doc: further shorten CLI examples using relative paths

due to this bug (I suppose), trying to generate the various mapping files for a compressed graph that also includes swh:1:ori:... PIDs fails with:

Pre-computing node id maps...
Exception in thread "main" java.lang.IllegalArgumentException: Unknown SWH ID type in: swh:1:ori:4135fe80baeff9983f73e94b02da92f618cbb6c7
	at org.softwareheritage.graph.SwhId.<init>(SwhId.java:44)
	at org.softwareheritage.graph.backend.Setup.precomputeNodeIdMap(Setup.java:108)
	at org.softwareheritage.graph.backend.Setup.main(Setup.java:47)

Here's a first stab at an API for the py4j bindings that would be nice to use.

Instead of this, please add a pair of private methods to the Endpoint class, one to start timing (e.g., this.startTiming()), one to end it and return the diff w.r.t. the start time (e.g., this.stopTiming()) , and make all endpoint methods invoke the two methods and log the result.

I was more thinking of lifting this up to the traversal algo, ideally not having to do a test at every edge that is followed.
Done this way, this is not gonna gain you much, only a couple of array lookup per edge.

in f13a43d697eb0d10ba59a4789847742607c49aaa I've added swh-graph to the mrconfig of swh-environment, let's see what the CI has to say about that… (cc: @douardda)

In D1741#40411, @haltode wrote:

Concerning links to swh-graph/docs it needs to wait for integration with swh-docs and then add external html links.

in addition to the comments below, a general issue is that all verbs are in the third person (e.g., "returns foo", "converts bla"), while it is more idiomatic to use the infinitive in API documentation (e.g., "return foo", "convert bla").

*SAD TROMBONE*.

In T1832#35429, @ardumont wrote:

If we agree that the status page is the way forward (and that clients interested in swh can use it to subscribe to update), i think we could close this current task now.

• use case doc: update edge restrictions for provenance use cases

• doc: add use cases and benchmark description
• use cases doc: fix typo and remove out-of-scope comments
• use case doc: update edge restrictions for provenance use cases

as a minor point on the commit message, I think you need separate Closes lines to close several bugs with a commit at once

• use cases doc: fix typo and remove out-of-scope comments