Build is green
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Sep 17 2020
Sep 16 2020
Drop unnecessary default configuration about log_db
Build is green
Fix and add tests about edge case (no default config provided during read call)
Sep 15 2020
Sep 14 2020
May 28 2020
Apr 21 2020
All swh modules updated with the runtime requirements stanza.
Documentation updated as well.
Apr 20 2020
Feb 11 2020
Feb 10 2020
Feb 7 2020
Jan 29 2020
Jan 28 2020
Jan 27 2020
Jan 22 2020
Oct 9 2019
Build is green
See https://jenkins.softwareheritage.org/job/DCORE/job/tox/304/ for more details.
Oct 8 2019
Aug 12 2019
Jul 10 2019
Jul 9 2019
Jul 8 2019
Jul 4 2019
Jul 2 2019
Feb 20 2019
Feb 12 2019
Feb 11 2019
Feb 1 2019
Jan 31 2019
Jan 29 2019
In T1499#27578, @douardda wrote:Note that I've modified the original file, so I'm not sure whether we should keep it (swh/core/api/negotiate.py) under its original MIT license (in which case the debian package's copyright file should be modified) or if we put it under the swh.core's LGPL one.
Note that I've modified the original file, so I'm not sure whether we should keep it (swh/core/api/negotiate.py) under its original MIT license (in which case the debian package's copyright file should be modified) or if we put it under the swh.core's LGPL one.
I agree we must be careful with not bloating swh.core, but the current subject, it really makes sense to me to put this basic db access wrapper as a core functionality.
Jan 24 2019
Dec 4 2018
Oct 30 2018
Oct 12 2018
as per discussion, we'd rather keep them self-contained than gain something out of code deduplication
Oct 11 2018
Oct 5 2018
Their content should be moved to swh.core.
May 25 2018
May 24 2018
May 23 2018
Dec 15 2017
You can add swh.indexer.storage.db.Db to your list.
Nov 6 2017
I disagree with the characterization of the default config as bogus. The default configuration is expected to work without change on a "developer" environment (e.g. point to a remote storage listening on localhost:5002, and to the "-dev" variants of any needed local databases).
Nov 2 2017
I disagree with the characterization of the default config as bogus. The default configuration is expected to work without change on a "developer" environment (e.g. point to a remote storage listening on localhost:5002, and to the "-dev" variants of any needed local databases).
Jan 26 2017
Aug 23 2016
May 13 2016
Mar 10 2016
Feb 29 2016
It looks like we've moved on onto this, and settled for what we have.
We can reconsider in the future if specific needs arise.