Query: All Stories

Add a 'swh provenance replay' cli command

Merge branch 'import-from-license-dataset'

FindEarliestRevision: Add earliest_ts and rev_occurrences columns

Give swhworker, olasd and ardumont direct access to tate for the GitLab…

	Include stories about projects I am a member of.

I see, it makes sense then.

cpan: Collect extrinsic metadata for each module release

cpan: Do not parse intrinsic metadata for getting module author

Implement `default-branch-name` in vc-repository model

merkle: Make MerkleNode.collect return a set of nodes instead of a dict

In D8678#226283, @douardda wrote:

In D8678#226223, @vlorentz wrote:

Bikeshedding: it should be called "journal-client" rather than "replay" for consistency with swh-indexer and swh-search. (swh-storage only calls it "replay" because it's used to copy from another instance of the same code so it "replays" the same API calls; but here it may be the first "play")

I'm not sure I follow you there; this really is a replayer feature: it aims at replicating a provenance DB via a kafka journal.
We already have a journal client in provenance consuming the main archive revision and origin-visit-status topics. The cli are swh provenance revision from-journal and swh provenance origin from-journal (aka execute the {origin,revision} layer reading from the journal; there are from-csv versions of these commands as well).

In D8678#226223, @vlorentz wrote:

Bikeshedding: it should be called "journal-client" rather than "replay" for consistency with swh-indexer and swh-search. (swh-storage only calls it "replay" because it's used to copy from another instance of the same code so it "replays" the same API calls; but here it may be the first "play")

This project has migrated to GitLab

Updated backport on buster-swh from debian/0.1.1-1_swh1 (unstable-swh)

Merge tag 'debian/0.1.1-1_swh1' into debian/buster-swh

pristine-tar data for swh-scrubber_0.1.1.orig.tar.gz

Update upstream source from tag 'debian/upstream/0.1.1'

Updated debian changelog for version 0.1.1

New upstream version 0.1.1

storage_checker: Notify database when ranges are fully checked

storage_checker: Do not re-check ranges already marked as checked

In D8682#226232, @vlorentz wrote:

That's a surprisingly small diff for such a change, nice!

What speedup do you get with this?

Repository archival is stored two different ways on phabricator

Screenshot of resources usage while test runs on my laptop:

Update: s/cpan-module-json/cpan-release-json/

Update:

use hash builtin instead of adding a new hash_to_int method
update tests

That's a surprisingly small diff for such a change, nice!

Bikeshedding: it should be called "journal-client" rather than "replay" for consistency with swh-indexer and swh-search. (swh-storage only calls it "replay" because it's used to copy from another instance of the same code so it "replays" the same API calls; but here it may be the first "play")

Enable ssh's control socket persistence

Assume repositories with a custom view policy are private

Don't force push on the master branch, which is protected

Actually perform repository archival at the end of the migration

rlog: Skip rlog entry with missing header in RlogConv.parse_rlog

loader, cvsclient: Read files line by line to reduce memory consumption

All Stories
Use Results
Edit Query
Hide Query

Oct 17 2022

All StoriesUse ResultsEdit QueryHide Query

Oct 17 2022

All Stories
Use Results
Edit Query
Hide Query