Build is green
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Jul 4 2022
Remove multiplier for connections; set complexity to 2
Build is green
cost for nodes
Build was aborted
Fix failed build: Corrects test in test_composer
Build has FAILED
Rebasing
Build is green
Build is green
Build is green
Build is green
Build is green
rebase + add migration
rebase
rebase + rename decorator
Build was aborted
Build was aborted
Build is green
rebase
rebase
Shouldn't there be a migration script as well?
update docstring
Build is green
Build is green
Build is green
rebase
rebase
update docstring and make commit msg more descriptive
ok but the wording of the mark_production decorator
In D8045#209752, @olasd wrote:AFAICT this function now does the detection itself, so maybe it deserves an update.
I'm not against this, but I have my doubts on the overall "architecture".
I'm slightly surprised by the change of signature for translate_directory_intrinsic_metadata without change to the docstring. AFAICT this function now does the detection itself, so maybe it deserves an update.
In D8048#209747, @douardda wrote:If this only test being moved or are there other (eg new tests) coming along? If so, please specify it in the commit message.
Don't like the zz-celery hack, but well, that's life. Did not check the new test files actually correspond to old test_metadata.py content. If this only test being moved or are there other (eg new tests) coming along? If so, please specify it in the commit message.
lgtm but it's missing the test case around it. It should not be too hard to add a
scenario which lifts the flavor parameter, shouldn't it? possibly, but I had it tested
from swh-storage (D8067)
Build is green
seaweed: replace with objid_to_default_hex
Ongoing on https://github.com/rdicosmo/updateswh, landing page is on https://www.softwareheritage.org/browser-extensions/
In D8066#209725, @ardumont wrote:lgtm but it's missing the test case around it. It should not be too hard to add a scenario which lifts the flavor parameter, shouldn't it?
Heads up, current work to improve the jenkins tooling has been tested (docker-compose,
jenkins in docker, triggering pipeline with docker).
lgtm but it's missing the test case around it. It should not be too hard to add a scenario which lifts the flavor parameter, shouldn't it?