Also I just realized, as it's not completely ready afaik, don't land it yet though.

Don't forget to add yourself to the top-level CONTRIBUTORS file ;)

^ Temporarily disabled puppet agent and bumped the concurrency for that worker to 10 (around the time of the previous comment).

Hey good people, this failing test [1] and the snapshot_id mentioned in the code actually work well on my local setup. How can it be that snapshot_id's are different on different hosts?
More specifically: snapshot_id on jenkins is 'ae8f76fe879ea040312182c02dae324a11252f83' and on my local setup is '677b0280cbe9e650c9dfa80fbb1ab7ebb1603c86'.

Build has FAILED

• maven jar-loader: fix + add tests.

Build is green

Rework commit message to fix typos and formulation.

Build is green

• pre-commit java file formatting change (fix commit message)

Build is green

Rework commit message

Discussing with the sysadm team, it's unnecessary to actually go up to package py4j.
What's required here for the vault the python3-swh.vault.client package with only the module swh.vault.client and swh.vault.naive_client.

Build is green

Update:

• fix test
• remove miscellaneous section and move guix/nixos origins into the regular crawling one
• implement functions to the get the guix/nixos origins count as there is no scheduler metrics for those

Ongoing ingestion is rather slow [1]
Because like for git origins, we can't know in advance rather large repositories.
So sometimes, ingestion appears stuck because we are dealing with large repositories (more than 2 hours of loading [2]).

In D6156#159397, @ardumont wrote:

I'd like to try back to install collected resources but as far as i recall my previous attempts
seemed to work in surface but the checks ended up being executed on pergamon (icinga2 master)
and not the nodes...

D6163 confirms this ^

Apply suggestion! And now the checks are working properly

"topics" (these are the "tags", right?)

Here's an opinionated and prioritized list.

Build has FAILED

In D6004#159479, @zack wrote:

quick comment on the "Miscellaneous" category:

• it's not a great name, and it really feels they are "less important" than the others even if we say explicitly they aren't (or maybe because we say so :-))
• and shouldn't the two items in there (nix, guix) go under "regular crawling" anyway? (that would trivially solve the previous point)

the rest LGTM

quick comment on the "Miscellaneous" category:

• it's not a great name, and it really feels they are "less important" than the others even if we say explicitly they aren't (or maybe because we say so :-))
• and shouldn't the two items in there (nix, guix) go under "regular crawling" anyway? (that would trivially solve the previous point)

Cool! LGTM

Update:

• Open search links in new browser tab
• Put coverage widget CSS rules in a dedicated file

@moranegg , @rdicosmo , after taking your comments into account, below should be the final design of the iframe view for content or directory:

In T3542#69656, @moranegg wrote:

At the moment, I think that all the properties you have selected in the task are needed.

Build has FAILED

• maven jar-loader: un-change loader.py (cleanup debug statements).

Build has FAILED

• maven jar-loader: fix tests.
• maven jar-loader: fix tests.

At the moment, I think that all the properties you have selected in the task are needed.
+1 for License (it is something they show on the interface even if it is based on a heuristic).

The key examples are computer museum websites: they will want to keep the visitor on their website, for visibility reasons, and we need to cater to their needs.
Typically, we should be able to provide them with an embedded view that looks like this (possibly without the "download" and "save again" buttons)

Build is green

Build is green

What task?

There is no longer any debian branches on the swh-graph repository, so this must have been done already.

 swh  tony  yavin4  ~  work  …  swh  swh-environment  swh-graph   master  1⚑  ERROR  %  git pull
Already up to date.
 swh  tony  yavin4  ~  work  …  swh  swh-environment  swh-graph   master  1⚑  %  git branch --remote | grep -i debian
 swh  tony  yavin4  ~  work  …  swh  swh-environment  swh-graph   master  1⚑  ERROR  %  git branch --remote | grep -i upstream
 swh  tony  yavin4  ~  work  …  swh  swh-environment  swh-graph   master  1⚑  ERROR  %  git branch --remote | grep -i pristine-tar

rebase

In D6143#159424, @vlorentz wrote:

In D6143#159345, @ardumont wrote:

As far as i understood, this is needed to allow development on swh-search.

Not needed, but very helpful

Shouldn't this be explained in the docs somewhere though?

What part?

rebase

In D6143#159345, @ardumont wrote:

As far as i understood, this is needed to allow development on swh-search.