commit 02bba328b22c2cb33c6cb6478f3e0b3d56aea5ea
Merge: b149f3021 74948a598
Author: Colin Watson <cjwatson@debian.org>
Date: Tue May 26 11:28:52 2026 +0000
Ignore DeprecationWarning from fakeredis (MR !3077)
This was fixed in fakeredis 2.30.1, but we can't do much about it when
running tests on trixie.
Merge-Request: https://salsa.debian.org/freexian-team/debusine/-/merge_requests/3077
commit 74948a598aa4b6ee2567eb4260ba9d3fd5e94b22
Author: Colin Watson <cjwatson@debian.org>
Date: Tue May 26 11:20:40 2026 +0100
Ignore DeprecationWarning from fakeredis
This was fixed in fakeredis 2.30.1, but we can't do much about it when
running tests on trixie.
commit b149f302146b4ece2879f2a8009e0ad44f3619d7
Merge: b02b01109 a01033fbf
Author: Stefano Rivera <stefanor@debian.org>
Date: Mon May 25 22:21:48 2026 +0000
Implement a redis-backed prometheus sample store (MR !3013)
This is a vendored version of the change forwarded here:
https://github.com/prometheus/client_python/pull/1170
It's adjusted to use Django settings instead of the environment (for simplicity).
Fixes: #1406
Closes #1406
Merge-Request: https://salsa.debian.org/freexian-team/debusine/-/merge_requests/3013
commit a01033fbf1ac0049e09f3365c2097350021d855f
Author: Stefano Rivera <stefano@freexian.com>
Date: Mon Apr 27 11:04:42 2026 -0400
Replace Prometheus multiprocess mode with our Redis implementation
commit 7bb539d95967ab9130a26d81eec8a110f2703da4
Author: Stefano Rivera <stefano@freexian.com>
Date: Sun Apr 26 23:19:09 2026 -0400
Implement a redis-backed prometheus sample store
This is a vendored version of the change forwarded here:
https://github.com/prometheus/client_python/pull/1170
It's adjusted to use django settings instead of the environment (for
simplicity).
commit b02b01109c8f05365b36d34030f49823db029d81
Merge: 79c21bb87 f07a8f229
Author: Stefano Rivera <stefanor@debian.org>
Date: Mon May 25 20:31:35 2026 +0000
CLI Client for Lookups (MR !3041)
Includes a lot of refactoring to make the results useable:
1. fix some obvious client model oversights
2. refactor the response classes (server and client side) to skip setting implied attribute values
3. rename result type values in the API to be human-readable
4. include more information in lookup API responses, from the CollectionItem table
5. include links in lookup API responses
Closes #691
Merge-Request: https://salsa.debian.org/freexian-team/debusine/-/merge_requests/3041
commit 79c21bb8797287cc1e0286ec75b478c6782c400c
Merge: 33ad842c9 1f4fc6175
Author: Colin Watson <cjwatson@debian.org>
Date: Mon May 25 17:25:10 2026 +0000
Make all regression-analysis callbacks incremental (MR !3007)
This substantially reduces the number of work requests we need to create
for large regression-tracking workflows: we only need one per
sub-workflow, not one per sub-workflow per architecture.
Part of #1412.
Merge-Request: https://salsa.debian.org/freexian-team/debusine/-/merge_requests/3007
commit f07a8f2299db86d1f8c1f757eddd22112410680e
Author: Stefano Rivera <stefano@freexian.com>
Date: Sat May 9 19:15:09 2026 -0400
CLI client for lookups
Fixes: #691
commit f17fe55f285991528891ffdb9df4bcac069b3b21
Author: Stefano Rivera <stefano@freexian.com>
Date: Wed May 13 18:52:18 2026 -0400
Add links to lookup results.
commit 6539652cb8c1f8fef23b3e8b1a134f6ecd8c5d0f
Author: Stefano Rivera <stefano@freexian.com>
Date: Mon May 11 18:10:05 2026 -0400
Enrich lookup API responses with collection item data
CollectionItems aren't accessible though the API, so include useful
collection item contents in the response, rather than a collection item
ID. Currently:
* `name`
* `data`
Additionally, expose the `parent_collection_lookup` from the lookup
result. Multiple lookup could return results from multiple collections.
commit c57c66e3691b0dfc89c87029656ff14ef9c7eb6e
Author: Stefano Rivera <stefano@freexian.com>
Date: Mon May 11 14:23:30 2026 -0400
Use a readable `result_type` in the Lookup APIs
We use a single character in the database, but we don't need to do that
in the API.
commit d0b03298413e34bf569946ed1e20d602c63db4b8
Author: Stefano Rivera <stefano@freexian.com>
Date: Sat May 9 18:55:31 2026 -0400
Don't use server-side models for lookups in the client
commit 2314cfe1e726ecc9d47d654fc1b328c1eb48a45c
Author: Stefano Rivera <stefano@freexian.com>
Date: Sun May 10 17:19:12 2026 -0400
Use a default result_type in LookupResult* objects
commit 27bd12d6b6cfda56aac710b660d72f36bacf39be
Author: Stefano Rivera <stefano@freexian.com>
Date: Sat May 9 17:52:37 2026 -0400
Treat LookupSingleResponse subclasses equally when evaluating equality.
commit 986946423cf2695eda375e090e53f0204a6cbb52
Author: Stefano Rivera <stefano@freexian.com>
Date: Sat May 9 17:43:00 2026 -0400
Set the only valid value as default in LookupSingleResponse subclasses
commit d416720af5589a2ef5916dcde41b1128857ee2d8
Author: Stefano Rivera <stefano@freexian.com>
Date: Sat May 9 17:41:26 2026 -0400
Set a sensible expect_type
commit e681d30570b2bcfb553db043ffdbd915f02cc828
Author: Stefano Rivera <stefano@freexian.com>
Date: Sat May 9 17:39:42 2026 -0400
A work_request does not have to be specified to LookupSingleRequest
commit 92567d2dd34780f13e5bc0caebf0d821834f63c1
Author: Stefano Rivera <stefano@freexian.com>
Date: Sat May 9 12:19:15 2026 -0400
Specify a workspace to process lookup API requests in
This must have been accidentally left out when they were implemented, as
the server will fall back to the default workspace.
commit 1f4fc6175a9099503819bcbceef8d609ee5f47bb
Author: Colin Watson <cjwatson@debian.org>
Date: Wed Apr 29 18:41:40 2026 +0100
Make all regression-analysis callbacks incremental
This substantially reduces the number of work requests we need to create
for large regression-tracking workflows: we only need one per
sub-workflow, not one per sub-workflow per architecture.
Part of #1412.
commit 06106043b51a5caeaf10881e7ba61c315561e421
Author: Colin Watson <cjwatson@debian.org>
Date: Wed Apr 29 17:09:14 2026 +0100
Simplify assert_regression_analysis interface
commit d44a945d14e0d15caf86088e9040dc1c29949d82
Author: Colin Watson <cjwatson@debian.org>
Date: Wed Apr 29 16:38:04 2026 +0100
Fix a flaky test
Automatic checks made by the Debian l10n team found some issues with the translations contained in this package. You should check the l10n status report for more information.
Issues can be things such as missing translations, problematic translated strings, outdated PO files, unknown languages, etc.
![[bug history graph]](https://qa.debian.org/data/bts/graphs/d/debusine.png){kind=link}