I don't like 1/ at all, and 2 seems indeed a burden for clients...

In D4758#119147, @vlorentz wrote:

Sorry @douardda, but I'm going to assume you are fine with this diff, because I'd really like this to work before Vincent goes on vacation

replace deprecated :show-nested: option by :nested:

and fix the click object name to document

fix the :prog: flag

It looks to me that this really about

rework the specs according to zack's comments (hopefully) + rebase

In D4698#117895, @vlorentz wrote:

I completely agree with @olasd 's comment.

And why is it restricted to revisions? Why not have an endpoint that returns an arbitrary SWHID?

In D4720#117920, @ardumont wrote:

@douardda Why the not on the version?

do not fix the pg version otherwise ok

split the commit in 3 parts

fix and improve the long int encoding examples

Question: who should be responsible for filling this table? The loader or the storage (as side effect of revision_add)?

Ok so the plan is a first step as simple as possible, implementing what @olasd proposed in the task, put this table in the storage, and provide a simple batch get API endpoint.

fix typing according to olasd's comment

In D4684#117170, @anlambert wrote:

Cool, thanks ! Can you push a new tag for swh-core once landed ? This will make swh-web CI happy.

and requirements-http.txt

ci msg

after this patch I have:

Also the "Currently" in not appropriate, there is not any chance the 7.10.0 will be updated, so the I'd get rid of the "currently" in this caveat entry description.

Not sure the debian specific part is needed here. It's only a transient problem that will hit very few (most probably swh team mate only) people.

not sure why this is needed but otherwise lgtm

(not sure why tests are red) lgtm

fix indentation pbs

In T2827#54141, @olasd wrote:

Just to be sure (I'm confused even after reading the history document), HedgeDoc is the *community* fork of the HackMD code base (which was named CodiMD), and has no relationship with the original upstream company running hackmd.io. Correct?

improve the doc

done for the journal. We might want to do the same in the RPC low level stack (swh.core.api), some day (or replace this later by gRPC or so :-) )

overall lgtm but see comments

Add a few tests for msgpack codecs (dates and long integers)

Improve (?) the commit message

Simplify a bit the bw compat code (no need for "genericity" there)

Use (poorly/not documented) timestapmp/datetime feature flags of mashpack to handle datetime objs

forgot to save before commit...

Update the documentation for (WIP) extended type based datetime encoding

can storage be easily added to the backup server?

Replace usage of arrow for its humanize() feature by the humanize module