rebased

rebased

In D4891#122658, @ardumont wrote:

This makes me wonder if we shouldn't add an explicit failed status too, while we're at it, for explicit failures that couldn't generate a partial snapshot.

I'd be fine with that indeed.

I think we entertain the idea with @douardda and @vsellier

lgtm

Looks ok to me. I'd like however to have a description of implemented metrics in the commit message (and in the documentation, but this may come later)

rebased

Use olasd's version os the SQL query

overall looks good to me, but it could benefit from more comments and explanations. Not easy to get in as is.

rebse

forget the migration script

lgtm

thanks, looks a good starting point.

rebase

rebase

Add a paragraph in the README file

same but with all files commited

fix hypothesis strategies tests

add a unique_key method to ExtID and some tests

Add unicity index and corresponding test

Rewrite SQL queries a bit better (thx olasd and vlorentz)

In T2089#49315, @moranegg wrote:

This list of user stories is something that can be written in a wiki.
@douardda or do you prefer having this list of scenarios in the docs ( for example in: docs.softwareheritage.org/user-stories)

Also, how is the authentication made?

I see in the inventory that this VM has 8GB of RAM and 64GB of storage, isn't it a bit overkill?

In T2779#55809, @vlorentz wrote:

If we can have metadata on metadata, then we can also have metadata on metadata on metadata, and metadata on metadata on metadata on metadata, ...

Refactor the API and implementation so ExtID are not created as part of revision_add()

I'm also having the "full journal" approach in mind after a quick reading of this neat proposal :-)

not finished, but first burst of comments

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: