Oh yeah, I was thinking of just removing the entire project, but your solution also works.

Do you actually want to keep these objects? This would be inconsistent with the fixed loader behavior that would just reject those objects, and not load the repository at all.

Partially solved by https://forge.softwareheritage.org/D8191

Opened https://github.com/vigna/dsiutils/pull/6 as a potential fix for https://github.com/vigna/dsiutils/issues/5

Fix URL

fix service path + rebase

GRPC update: cancelling a GRPC stream works fine, but it doesn't seem like aiohttp is doing that when the HTTP stream is closed.

We requested a larger quota here: https://github.com/pypa/pypi-support/issues/1998

We are migrating away from Debian packages as a deployment tool, closing this as WONTFIX.

We are migrating away from Debian packages as a deployment tool, closing this as WONTFIX.

No longer happens after the GRPC migration:

We removed the Py4J dependency by migrating to GRPC.

We no longer support multiple algorithms for shortest path requests.

Obsoleted by the migration to GRPC. Now we use GRPC's threading model, with a threadpool configurable by passing --threads to the Java service. By default, nproc is used.

Obsoleted by the migration to GRPC. We no longer create iterators on the decoded stream of a UNIX pipeline, we directly use GRPC stream iterators.

Fixed by the migration to GRPC.

rebase

• Generate .labelobl files to speed-up labelled graph loading

Fixed in D8050

Fix ranges