Thanks for your time and interest.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Sep 21 2021
Sep 20 2021
complete other tools section
- fix a couple of staging urls
- add the production urls
Do you reference only the staging part?
fix typos
ok, nice start.
Do you reference only the staging part?
If we want to add this, we should also add it to test_pattern.py tests (which check that the scaffolding actually runs as expected). The documentation of the main pattern class also needs to be updated to add a reference to the new method.
I've patched the systemd swh-worker@loader_oneshot to actually lift --autoscale 10,20
from celery cli. It's actually holding fine. And that coupled with the filtering server
side makes for a huge bump in speed. The archive db does not seem to mind at all.
Given the D6306 rework, this requires a bit of change (but nothing too drastic).
Build is green
Build is green
Build is green
Build is green
Rebase
Rebase
- Adapt to be multi instance aware
- Rebase on top of other diffs
Add missing doc about new note field in apidoc for /origin/save/
Build is green
Adapt test docstring into a todo since it's actually a todo
LGTM, but how is the new opam_root option expected to be set (in production I mean)?
LGTM, but how is the new opam_root option expected to be set (in production I mean)?
I'm not done yet but here is first review on my side.
swh:1:dir:880034219b47a123b97161de4e0d3301746cec75 (from https://github.com/kentnl/Dist-Zilla-PluginBundle-Author-KENTNL) has a single entry; we stored it with mode 40000 on that entry, but the original mode is 40755.
Deployed the multiple fixes we did with @anlambert.
That and @mclovin's upstream fixes. We should be good.
italic text
oops ;)
10:02:40 softwareheritage@belvedere:5432=> select now(), count(distinct url) from origin o inner join origin_visit ov on o.id=ov.origin where o.url like 'https://bitbucket.org/%' and ov.type='hg'; +------------------------------+--------+ | now | count | +------------------------------+--------+ | 2021-09-20 10:04:30.89072+00 | 280995 | +------------------------------+--------+ (1 row)
Deployed the loader mercurial v2.3 (with filtering server side).
As expected, less time is spent in the method fetching the new changesets.
Fix [1] first
not useful as a dedicated task, see T1805 for the main discussion one on this subject
In D6291#163149, @aeviso wrote:I'm not really convinced about adding this test, it essentially recreates situations that are already tested in the test_provenance_storage test (but there it is done for all backends at once).
Also, performing direct queries to the mongodb object breaks the abstraction layer which means any future refactoring will require reimplementing this tests.
I rather design test to be independent of the actual implementation, so that they check that the class behave as expected from a semantic point of view.
I'm not really convinced about adding this test, it essentially recreates situations that are already tested in the test_provenance_storage test (but there it is done for all backends at once).
Also, performing direct queries to the mongodb object breaks the abstraction layer which means any future refactoring will require reimplementing this tests.
I rather design test to be independent of the actual implementation, so that they check that the class behave as expected from a semantic point of view.
anomad-d is the user-repository name. It's a repository which presents an anomaly in some way. That anomaly makes the ingestion fail.
I don't understand what exactly is (not) tested here. What does "anomad-d" stand for BTW?
Build is green
string changes
Sep 19 2021
The agreement has been signed, so we can move forward and publish the blog post.