- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jan 8 2023
Nov 28 2022
Oct 19 2022
Oct 11 2022
Oct 10 2022
Oct 7 2022
Sep 9 2022
Jul 22 2022
FWIW I've also started the provenance storage server as a systemd system service now.
I've granted mmca access to the production journal for user swh-provenance-mmca.
I've added an autossh-mmca.service unit on belvedere to have a reverse tunnel from localhost@mmca:5345 -> localhost@belvedere:5432.
Jun 28 2022
Jun 27 2022
Jun 17 2022
A dozen of clients running in the provenance-client01 are using the multiplexer configuration.
It seems to work correctly
Jun 16 2022
Build is green
Update according the reviews
- Add and fix license headers
- Ensure the _revisions_count variable was computed before returning its value
Jun 15 2022
(oops, forgot to validate it yesterday ;)
Jun 14 2022
Jun 8 2022
fixed with the workaround in D7972
Jun 7 2022
Jun 4 2022
This issue was a false lead, different snapshots are declared for the same origin letting me believe there were some duplicates.
I completely missed it and fall head first into the trap
Jun 3 2022
after some ingestion time, it seems the first analysis is wrong:
(provenance) provenance-client01:~$ sort ~/origin-client.log |grep Processing | uniq -c | sort -n | tail -n 10 6 INFO:swh.provenance.origin:Processing origin https://bitbucket.org/360factors/workflow-conditions.git 6 INFO:swh.provenance.origin:Processing origin https://bitbucket.org/4s/cda-document-viewer.git 6 INFO:swh.provenance.origin:Processing origin https://bitbucket.org/4tic/goc.git 6 INFO:swh.provenance.origin:Processing origin https://bitbucket.org/ALEXks/sapfor_2017.git 6 INFO:swh.provenance.origin:Processing origin https://bitbucket.org/ASIWeb/testcomplete.git 7 INFO:swh.provenance.origin:Processing origin https://anonhg.netbsd.org/xsrc-draft/ 7 INFO:swh.provenance.origin:Processing origin https://anonhg.netbsd.org/xsrc-public/ 8 INFO:swh.provenance.origin:Processing origin https://anonhg.netbsd.org/xsrc/ 13 INFO:swh.provenance.origin:Processing origin https://bitbucket.org/9front/plan9front 20 INFO:swh.provenance.origin:Processing origin https://anongit.kde.org/kdenlive.git
Jun 2 2022
It's not as bad as expected, it seems only 2 clients are proceeding the same origin at the same time:
May 25 2022
May 11 2022
Apr 19 2022
Mar 31 2022
Mar 25 2022
Mar 23 2022
Dec 6 2021
Nov 4 2021
2M with unique sha1 index (Embedded arrays with bulk write on content and directory)
(Exited after 542,000 of memory errors)
Postgres: 10k with sha1 index (Embedded arrays with bulk write on content and directory)
python client.py -n 4 -C config.yml
Postgres: 10k with sha1 index (Embedded arrays without bulk write)
python client.py -n 4 -C config.yml
Sep 6 2021
Initial version is merged to master.
First test 07/09/2021
Against the simple/experimental data model version. (https://forge.softwareheritage.org/rDPROV3e009a2f77de1d4d00eb52f838537c7af327f010)
Computer: Dell 7400
Aug 25 2021
Build is green
MongoDB backend implementation for provenancestorage.
Build is green
- Added the necessary directory for mongo pytest to work
Build has FAILED
MongoDB backend implementation for provenancestorage.
Build has FAILED
- Made default provenance storage to psql
Build has FAILED
- Pytest is using mongomock