Miner/index on objects contained the Software Heritage archive.
Tue, Feb 25
Mon, Feb 24
Thu, Feb 13
Tue, Feb 11
Fri, Feb 7
I think it qualifies, yes
@vlorentz I'm not sure it is an easy hack, could you review the task and decide?
Tue, Feb 4
Yes, but you should just open a diff instead.
And does Jenkins also run code in non-master branches through the pipeline?
Mon, Feb 3
and apologies for the delay.
Sun, Feb 2
Thanks for the detailed reply 🙂, and apologies for the delay. Things are clearer now 👍
Sat, Feb 1
hey, I would like to contribute.
The pytest tests are succeeding in the swh-indexer module, but failing in some other modules. Since this issue pertains to only the swh-indexer module, it shouldn't cause problems, right?
Hi, I'd like to take up this issue as my first issue here :) . But before I take it up, I just had a few queries:
Wed, Jan 29
Jan 27 2020
Jan 23 2020
sample with our shiny sentry: https://sentry.softwareheritage.org/share/issue/f4a40625783b4a5588980005ddc5a5e6/
Jan 22 2020
Jan 13 2020
Dec 20 2019
Dec 3 2019
Dec 2 2019
Nov 22 2019
Fixed by D896.
Nov 14 2019
Does it still happen? The journal client changed a lot since this task was open, including switching backend library.
Nov 8 2019
Fixed by @olasd
Nov 5 2019
Sep 30 2019
That's the postgresql statement_timeout variable that we set for some methods on the storage backends.
Sep 27 2019
We can investigate 2 things:
- check postgresql options to kill queries that takes too long (solely indexer-db right now) -> and find some way to report those
- push the proxy client storage idea (started within the T1389 for the storage, currently wip) up to the indexer-storage.
Sep 24 2019
Note: ... comments stack pop ... (-> been there a while apparently)
Sep 6 2019
In the end, it was missing initialization data steps.