Everything looks fine and visit-stats is growing gently:
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Today
Build is green
Build is green
Inline unecessary indirection
Build is green
Add missing test coverage
Rename "singleton" to "record"
for the sake of my questions
(i don't know why or if it's sensible that the decorator got dropped though ;)
Build is green
Build is green
Rebase
Build is green
Rebase and remove conftest.py file
sgtm
Build is green
Reword commit
Build is green
Rebase
Looks good but the commit message could be more detailed and rephrased to something like:
Back on this, the plan is now to make swh-journal not depend on the actual model definition, which is currently mostly due to the presence of the journal_data.py in swh-journal. So the plan is to move this file in swh-model so it's kept up to date with swh-model, even if it's mostly used for testing other packages (like swh-journal).
Build is green
Adapt according to review to improve readability
Looks good to me ! I added a comment regarding further improvements that could be added to the lister but not related to that diff.
Build has FAILED
commit message
Build is green
Rebase
Following URLs are now redirected to the desired page:
Build is green
oh, that explains the test failures, thanks
Rebase
Build is green
Add implementation instructions to the template
- getty: Update swh dependencies (storage upgrade for the backfiller)
for context: this change is only going to be committed in a separate branch that we're using for experiments with swh-scanner, hence the testing requirements are different/lower than for master
Nitpick: could you reword the commit to follow this guideline?
Build is green
Update: Add test for parse_packaged_date and fix implementation.
- Create consumer group swh.scheduler.journal_client so it starts at the end of the topics
Build is green
Update: Address some @tenma comments
Build is green
Build is green
address suggestion, ensure last_update field in listed_origin are not None
Use supported authentication scheme (bearer token in Authorization request header)
Build is green
Build is green
Build is green