Snippets Groups Projects

Forked from Platform / Development / swh-vault

11 commits behind the upstream repository.

backend: Force bundle recooking if it is no longer in cache

Antoine Lambert authored 8 months ago

It can exist cases when a bundle has been cooked and marked as done in
the vault database but is no longer available in the vault cache.

Previously, when requesting a new cooking of such bundle, the vault
backend was not creating a new cooking task and thus the bundle could
not be downloaded anymore.

So ensure to check bundle presence in cache for such edge case and force
its recooking if it is not the case.

Related to swh-web#4804.

8c89dcd8

8c89dcd8 8 months ago

Name	Last commit	Last update
docs
swh/vault
.copier-answers.yml
.git-blame-ignore-revs
.gitignore
.pre-commit-config.yaml
AUTHORS
CODE_OF_CONDUCT.md
CONTRIBUTORS
LICENSE
Makefile
README.rst
conftest.py
mypy.ini
pyproject.toml
pytest.ini
requirements-swh-graph.txt
requirements-swh.txt
requirements-test.txt
requirements.txt
setup.cfg
tox.ini

Software Heritage - Vault

User-facing service that allows to retrieve parts of the archive as self-contained bundles (e.g., individual releases, entire repository snapshots, etc.) The creation of a bundle is called "cooking" a bundle.

Architecture

The vault is made of two main parts:

a stateful RPC server called the backend
Celery tasks, called cookers