- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Sep 29 2020
Build has FAILED
Build has FAILED
fix commit message
Build was aborted
rebase
Build is green
Update docs
Build is green
Build is green
Build has FAILED
Build is green
Update: Remove empty line
improve commit message
Build is green
LGTM
everything is now better.
Rebase
I can vagrant ssh test though.
Build is green
In D4068#100955, @douardda wrote:LGTM (except the "rm -f ../$module.log " for which I am not convinced it's a good idea)
(just updated my swh-env, now I see where this diff comes from :-) )
Build is green
- Use list of swhids as input CLI
- Log error when fetching unknown SWHID
Build is green
sure
LGTM (except the "rm -f ../$module.log " for which I am not convinced it's a good idea)
I've sent an email to the fsfe.
Build is green
- Remove types from documentation (redundant with type hints)
- Move pyfuse3_asyncio.enable() in the main
- Small code clean up
use case for is client code that just want to access the raw JSON answers, as it is the case for the FUSE implementation
Build is green
Fix deposit client part (this parses the unchanged xml output so the fields should stay the old names)
Build is green
And the first line of the commit message should be changed; it should say what was changed, not just what components were changed
Following D4072, i now have another failure:
Build is green
Use sqlite context manager instead of manual commit
Build is green
Add documentation + type hints