- Aug 05, 2022
-
-
Jenkins for Software Heritage authored
-
Jenkins for Software Heritage authored
Update to upstream version '1.5.1' with Debian dir aecb33b9607d268dc35fe135a46a97eab940b3e5
-
vlorentz authored
-
vlorentz authored
The postgresql implementation uses '3 months', which is closer to 13 weeks than to 12 weeks.
-
vlorentz authored
start is increased from 13 to 14, because 13 weeks is 91 days, ie. 30+31+30; so it is sometimes smaller than 3 months. This was only hit rarely because the number of visits was small, so this commit also increases the number of visits to make the test more likely to fail if it should actually fail.
-
Jenkins for Software Heritage authored
-
Jenkins for Software Heritage authored
Update to upstream version '1.5.0' with Debian dir 34ae119254de09bf2789c8e454ecae8cb67a614d
- Aug 04, 2022
-
-
vlorentz authored
They are very noisy, and clients are expected to retry a few times before re-raising the exception on their side.
-
vlorentz authored
This caused the following warning: ``` WARNING cassandra.protocol:libevreactor.py:361 Server warning: `USE <keyspace>` with prepared statements is considered to be an anti-pattern due to ambiguity in non-qualified table names. Please consider removing instances of `Session#setKeyspace(<keyspace>)`, `Session#execute("USE <keyspace>")` and `cluster.newSession(<keyspace>)` from your code, and always use fully qualified table names (e.g. <keyspace>.<table>). ``` This also prepends 'test' to the name of keyspaces used in tests, so they are guaranteed to start with an letter (starting with digits cause syntax errors in most statements).
-
vlorentz authored
-
vlorentz authored
This reproduces what I think is the issue found in https://jenkins.softwareheritage.org/job/debian/job/packages/job/DSTO/job/gbp-buildpackage/423/consoleFull This does not fix the issue as it is a consequence of the design, but documents this problematic behavior.
-
Jenkins for Software Heritage authored
-
Jenkins for Software Heritage authored
Update to upstream version '1.4.2' with Debian dir 9e4f8fb309e3513a2cc36f0dd6a80fb264910e05
-
- Jul 13, 2022
-
-
Antoine Lambert authored
Even if missing index to speedup origin visit queries has been added to replica database, the configured timeouts for origin_visit_get_with_statuses and origin_visit_find_by_date were still too low to avoid query timeouts in production. After performing some tests locally, bumping them to 2000ms makes the timeouts go away. Related to T4386
-
- Jul 12, 2022
-
-
vlorentz authored
This uses Directory.from_possibly_duplicated_entries() to mangle entry names instead of crashing.
-
- Jul 08, 2022
-
-
David Douard authored
-
- Jul 06, 2022
-
-
David Douard authored
when the OriginVisit object given as argument to be inserted already have its visit id set (which is usually the case in a replayer-like session), it makes no sense to auto-add the first OriginVisitStatus objects related to this visit; this behavior is expected only when the origin_visit_add() is called from a loading session. Adapt tests accordingly -- several tests did depend on the auto-add behavior of the origin_visit_add method for OriginVisit objects which visit_id is given in the test dataset.
-
- Jul 01, 2022
-
-
David Douard authored
and add tests for 'mirror' and 'read_replica' flavors.
-
David Douard authored
-
- Jun 03, 2022
-
-
Jenkins for Software Heritage authored
-
Jenkins for Software Heritage authored
Update to upstream version '1.4.1' with Debian dir dbb991421736a20fe750987037213b265bfc0620
-
Antoine R. Dumont authored
This also simplifies the db collaborator code reusing core.db functions to check the code version and the actual db version matches. Related to T4305
- May 31, 2022
-
-
David Douard authored
instead of swh-core's postgresql_fact one, since we actually do not use its custom features any more in swh-storage.
-
David Douard authored
-
- May 10, 2022
-
-
vlorentz authored
-
- May 09, 2022
-
-
Pratyush authored
-