Do you mind if I claim this task?
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Oct 22 2018
Done in D490.
Oct 19 2018
Oct 18 2018
Oct 15 2018
Actually, this won't be needed, we can use BaseIndexer.next_step to schedule new Celery tasks.
The deployment of the RevisionMetadataIndexer will be correlated with the deployment of the OriginMetadataIndexer when the workflow is ready on a new separated task.
Oct 12 2018
Oct 11 2018
Oct 10 2018
Oct 9 2018
Oct 8 2018
Oct 4 2018
Oct 3 2018
As an implementation strategy, I think we can aim at:
That would allow to be closer to use the real scheduler (swh-scheduler) [1] and not the volatile one [2]
Sep 28 2018
Sep 7 2018
Sep 6 2018
First batch is done: 3.7 billion [1]
Jun 25 2018
Status on this, replication up and running.
Jun 15 2018
Status on this, running cluster and db ;)
about us moving away from pg_logical replication (and targets the page about the new one [2]).
Replying to self here as well.
Jun 14 2018
Thanks again for your contributions.
Jun 13 2018
Relatedly, fixed/adapted according to latest use to provision a new node:
Jun 11 2018
Jun 8 2018
Jun 6 2018
In T782#20044, @zack wrote:
Apr 20 2018
"zack (Stefano Zacchiroli)" <forge@softwareheritage.org> writes:
Apr 18 2018
In T782#18978, @s wrote:
Apr 16 2018
@ardumont, Can I:
Mar 21 2018
Mar 17 2018
Mar 16 2018
Mar 14 2018
Dec 21 2017
Dec 14 2017
Dec 13 2017
Heads up, the output was too verbose so i updated that script to only show the last sha1 sent for computations:
After adding indexer dependency on the scheduler setup (rSPSITEfb6faecaaa928c4ddcbdbc81181bf3ffac2ace4c), this has been rescheduled through: