Allow incremental lister to actually start properly the first time
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jun 23 2019
Will also split this into 1 diff per commit.
Jun 22 2019
Build has FAILED
Jun 21 2019
In any case, still no longer works today. So might be time to fix it or remove it altogether (if unused and fix solely the incremental one).
So i believe the full lister implementation never worked (looks like a copy/paste from github lister's, db_partition_indice implem. cannot work here).
Jun 20 2019
So i believe the full lister implementation never worked (looks like a copy/paste from github lister's, db_partition_indice implem. cannot work here).
The incremental one is mostly ok though (as already mentioned, it's not complete).
@douardda As discussed orally, as i was unsure it ran at the time, I checked and yes.
We have data in the swh-lister db (~214 entries listed in table bitbucket_repo).
It ran around 2017-06-28 13:13:30.077108 (most probably prior to the scheduler existence).
Jun 19 2019
Jun 18 2019
Heads up, a priori, there is a bootstrap step missing.
@olasd told me it's possible we need to start an incremental one first (thanks).
Ok, so without further ado, removing the incremental phabricator lister.
It does not really exist.
From swh-lister db, all "main" instances listed:
Might be a flaky thing somewhere in our stack.
Rescheduling that task and it worked.
docker-run tryout for that same forge was fine.
Related T1801
Well, yeah, the real forge is https://developer.blender.org!
Migration done.
Jun 17 2019
Build is green
See https://jenkins.softwareheritage.org/job/DLS/job/tox/196/ for more details.
- phabricator.lister: Use credentials setup from configuration file
And no, too optimistic:
@anlambert how did you add an account in kde's phabricator forge?
(You mention tests on it in D1365)I don't find a registering link from their forge ;)
Jun 16 2019
Okay, @nahimilega Thanks. Will submit the correct patch soon
We need three backquotes after the line
@nahimilega I think I can work on this. Do you want the whole text after lister gnu into its own distinct block ( using triple backquote)
Jun 15 2019
I did a bit investigation on data dumps, and it seems, they can serve the purpose well
To get the package release, we mainly need the name and version of packages. The link can, therefore, can be generated as -
Jun 14 2019
Build is green
See https://jenkins.softwareheritage.org/job/DLS/job/tox/191/ for more details.
I've splitted the task in 2.