Build is green

fix spec of author/committer formatting in revision_identifier + update function name in ValueErrors raised by TimestampWithTimezone.from_dict

It should be reStructuredText (introduction here: https://www.sphinx-doc.org/en/master/usage/restructuredtext/basics.html ), with a reference from the toctree in docs/index.rst

yes, that's the plan

Nevermind, I was confused by all the red and it's much clearer what's left over in a text editor.

Build is green

Build is green

In D6165#164092, @vlorentz wrote:

It could be something like these:

• https://docs.softwareheritage.org/devel/architecture/metadata.html
• https://docs.softwareheritage.org/devel/architecture/overview.html
• https://docs.softwareheritage.org/devel/swh-model/data-model.html

You can start from your Hedgedoc document, remove the description of the current state, but keep the description of the new design and the rationale

rebase

rebase

documentation of what?

Build is green

rebase

It could be something like these:

In D6165#164089, @vlorentz wrote:

In D6165#163810, @aeviso wrote:

It's actually explained in the document:

Oh, sorry, I missed the hedgedoc link. I only looked in the repo and the diff's content.

Could you document the new design in this diff too, in the docs/ folder?

Well except both sides show deleted documentation, which can't be right :P

In T3602#71092, @vlorentz wrote:

Instead of running tests only with the pg backend, what about both the in-mem and pg, using a parametrized fixture?
This would allow catching discrepancies between backends, instead of accidentally relying on pg's.

And, as the in-mem backend is much faster, we could exclude the pg backend while iterating (eg. pytest -k 'not postgresql').

Instead of running tests only with the pg backend, what about both the in-mem and pg, using a parametrized fixture?
This would allow catching discrepancies between backends, instead of accidentally relying on pg's.

In D6165#163810, @aeviso wrote:

It's actually explained in the document:

All referenced heptapod instances listed.
Closing this.

Deployed v2.3.1 with that fix.

Build is green

Build is green

It's technically correct: when I split a file, it considers it to be a copy followed by deletions.

Build is green

Rebase

Rebase

Landed through ef502bc

apply comments

Thanks, let's deploy this so we can ingest properly now.
I notice it happens once in a while in the bitbucket origins.

LGTM!

• Ingestion mostly done (2 git origins remains to be done but the 99% of hg origins are done).. [1]
• archive changelog updated

Build is green

Drop spurious pdb

Build is green

Proper fix

Looks like Phabricator is doing a funny one when displaying this diff. Lemme check what's actually in the staging repo...

Interesting documentations on how to manage jobs:

• the different job pattenrs: https://kubernetes.io/docs/concepts/workloads/controllers/job/#job-patterns
• Using controllers to manage the workload: https://kubernetes.io/docs/concepts/architecture/controller/

LGTM

@Alphare any clues as to why the format here is not in sync? ^

Ok, found where the wrong format is found somehow, the branching_info.bookmarks is not in the right format.

The test helped, it's a mismatch format problem.
Uncomment the test, place the right pdb stanza in the code and behold:

Comment at the wrong position: T3599#71039

Listing and partial ingestion ok in staging.
Deployed on production (reduced to a minimum of 4 workers with concurrency 1).
Ingestion ongoing.

I believe most annotations for the *_git_object functions should formally be Unions. I think the fallbacks from dict should raise DeprecationWarnings too?

This is done:

• Archive changelog updated accordingly.
• We now have 2 heptapod instances listed (ingestion done) [1]

Heads up on this task, i'm actually waiting for the bitbucket ingestion (which is going faster now) to finish.
To re-use our worker17 to make one last run on all the mercurial origins.

I've patched the systemd swh-worker@loader_oneshot to actually lift --autoscale 10,20

Tested on staging and listing then (partial) ingestion went fine.
Triggered on production.