- Jul 23, 2021
-
-
Jenkins for Software Heritage authored
Update to upstream version '2.7.0' with Debian dir 6b15a8156e4b0b1122df1ae88f663dd3f0956acb
-
Nicolas Dandrimont authored
This allows distinguishing multiple potential versions of the mapping between external objects and their counterparts archived in Software Heritage, for instance when a loader has a backwards-incompatible change that should result in objects being loaded again. The field defaults to zero, in which case it's backwards-compatible with the previous implementation in terms of identifier computation.
- Jul 02, 2021
-
-
Jenkins for Software Heritage authored
Update to upstream version '2.6.4' with Debian dir 92f45f224d492f3f0b914e640c27ce17d2a9dcb7
-
Daniele Serafini authored
- Jun 25, 2021
-
-
vlorentz authored
We agreed a while ago they should be IRIs and not just URIs. This will trigger crashes in swh.storage.cassandra, as currently expects (wrongly) that origin urls are ASCII.
-
vlorentz authored
* empty fetcher name or version is not accepted by cassandra (and is nonsensical anyway) * ditto for non-ASCII (and any non-printable is nonsensical) * null bytes/chars are accepted by neither postgresql or cassandra
-
Jenkins for Software Heritage authored
Update to upstream version '2.6.3' with Debian dir 216fcda7a93684ee59ff01a0c7f8fc6021ad0e72
-
Jenkins for Software Heritage authored
Update to upstream version '2.6.2' with Debian dir df6eb8e5ae3566559bfc86ac892acd3504dc130b
-
- Jun 21, 2021
-
-
Daniele Serafini authored
Closes T3393
-
- Jun 16, 2021
-
-
Jenkins for Software Heritage authored
Update to upstream version '2.6.1' with Debian dir de4cc1005c62c873540e9c8b8067233771377a1f
- Jun 15, 2021
-
-
Daniele Serafini authored
- add typing annotation to avoid such error in the future Fixes T3383
-
Jenkins for Software Heritage authored
Update to upstream version '2.6.0' with Debian dir a5928cf48b5ed5e74f56196c93fd182d82f7589a
-
David Douard authored
-
David Douard authored
the problem was for datetime<epoch, the timestamp is negative, but since it's a float that includes the microseconds, if both are true (< epoch and microsecond > 0), then the computed (int) timestamp was off by one. Add dedicated tests for this.
-
- Jun 11, 2021
-
-
Daniele Serafini authored
-
- Jun 09, 2021
-
-
Antoine Lambert authored
-
- May 20, 2021
-
-
Jenkins for Software Heritage authored
Update to upstream version '2.5.1' with Debian dir 7de8b2d4d70f1a04bd64715de0a11f2f538c8fe1
- May 19, 2021
-
-
David Douard authored
make sure the snapshot id in OriginVisitStatus refers to existing Snapshot objects.
-
- May 11, 2021
-
-
Jenkins for Software Heritage authored
Update to upstream version '2.5.0' with Debian dir 05035d9eb3380a44d4daa228462b7349d05b90b7
-
vlorentz authored
The git_object is what will be actually useful to the vault. It's also easier to test, because test_identifier.py has the entire git_object in its test data.
-
vlorentz authored
Before this commit, manifests were only computed internally before hashing, so they were not available to outside modules. This makes testing the module very painful, because identifier functions can only be tested by checking the hash; so test failures did not show mismatches between the computed manifest and the expected one. Additionally, the 'git bare cooker' of the vault is likely to use these as well, as it needs to format git objects in the same format.