- the default branch for snapshots is defined to be HEAD.
- if the concept of HEAD exists with the same name in the upstream VCS (f.e. git, svn), this branch should be a literal pointer to the corresponding archived object
- if the concept of HEAD doesn't exist with the same name in the upstream VCS (f.e. mercurial), this branch should be an alias pointing at the default branch, named using the upstream VCS context (f.e. in the mercurial case, that would be an alias for the tip of the default branch)
- if the concept of a default branch/version doesn't exist in the upstream VCS, no HEAD branch should exist in the snapshot
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Oct 10 2018
Oct 4 2018
agreed, they should be removed (I've updated the task title accordingly)
Oct 3 2018
All the old visits have now been migrated to snapshots.
Sep 30 2018
And also make sure the one visit date is the right one:
Sep 28 2018
Sep 27 2018
Sep 21 2018
I added T336 as parent so that the save code now is deployed only when this one is fixed.
Sep 20 2018
Related D409
Sep 19 2018
That's been done for a while now.
Sep 12 2018
Spot checks:
Aug 24 2018
Heads up on this btw.
Aug 22 2018
Last edit to write all data to "temporary" table prior to actually cleanup (it was only done for release and snapshot so far. It's also done for origin_visit and fetch_history now).
Aug 3 2018
Jul 26 2018
In T1158#21531, @ardumont wrote:
Local tests are fine.
I added T336 as parent so that the save code now is deployed only when this one is fixed.
Last edit [1] to update code comments.
P286 is still wip as some now unclear exception occurs.
Jul 25 2018
P286 is still wip as some now unclear exception occurs.
To find those releases:
Jul 19 2018
Jun 19 2018
Jun 6 2018
Apr 12 2018
Mar 21 2018
$ cat ~/.config/swh/kibana/query.yml indexes: - swh_workers-2018.03.*
why no errors reported at all in logs (or logs for that matters..., removing all filters, this seems to stop around the 7th of march 2018)
Current status, the queue is empty.
Mar 19 2018
Mar 16 2018
Mar 14 2018
Finally, rescheduled using swh-scheduler.
Heading towards T986.
As in https://forge.softwareheritage.org/T879#16396, a limit of 2Gib on dump size was used to separate origins.
The current lists are stored at:
Mar 5 2018
As this is not a bug, I am closing that task.
Mar 2 2018
This example comes from parmap, see https://github.com/rdicosmo/parmap/
Thanks for the report. I haven't looked into this specific, so it's indeed possible it's a bug, but in the general case this is potentially normal behavior.
Branches can point to either releases or revisions (or, in fact, anything at all).
In the Git case, which looks like your case comes from, if one simply does a "git tag", that would create a ref pointing to a revision; whereas if one does "git tag -a" (annotated tag), that would create a release object (pointing to a revision) and a ref pointing to the release object. So an author that switched from using "git tag" to use "git tag -a" would justify what you have seen.
Feb 24 2018
Feb 23 2018
Status:
- [DONE] backup
- [IN-PROGRESS] Clean up in progress
Feb 21 2018
Thanks for the heads up.
FWIW the backup has now completed.
I agree with taking tags from both sides and discarding all lines that don't fit the pattern.
Feb 20 2018
postgres@prado:~$ pg_dump --format tar --table revision_history --table revision softwareheritage | gzip -c - > /srv/remote-backups/postgres/T970/revision-revision-history.tar.gz
Running a full backup of the table for the handful of revisions concerned here is a bit overkill! (better be safe than sorry and all that, but still...)
In T976#18114, @ardumont wrote:In any case, we need to make a backup dump prior to touching those tables!
Backup running on prado:
postgres@prado:~$ pg_dump --format tar --table revision_history --table revision softwareheritage | gzip -c - > /srv/remote-backups/postgres/T970/revision-revision-history.tar.gz
In any case, we need to make a backup dump prior to touching those tables!
- We can 'simply' delete the revision of type 'hg' as no other mercurial revision exists as of today.
Feb 16 2018
I've chosen 3. to comply with the doc's suggestion.
As usual nothing is set in stone.
Well, sure, if the .hgtags is corrupted...
Last relevant error found in crossing multiple streams... (noooooo).
I have a problem in the log fetcher (that's why it's said to be incomplete in the task description).
I have a problem in the log fetcher (that's why it's said to be incomplete in the task description).
"PatoolError('error extracting /srv/storage/space/m": 19,