Dependabot uv job times out and tries to update workspace members

Ouverte
#7,457 2 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 3 jours

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
45/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
github-actions, python, yaml
Domaine
build-system, devops

Piste de recherche

Start by reading .github/dependabot.yml and the root pyproject.toml workspace configuration; the linked Dependabot run shows the failure and timeout. Compare the two proposed approaches: renaming internal distributions or generating and validating the ignore list. Done means Dependabot skips workspace members and the weekly uv update completes without timing out.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

The weekly Dependabot uv update for / has been timing out or failing since early November (e.g. https://github.com/mozilla/bugbug/network/updates/1694419512).

Two causes:

  1. Dependabot treats uv workspace members as PyPI packages. testrail-client exists on PyPI (0.1.2), so Dependabot tries to "update" our 0.1.0 workspace member and fails with dependency_file_not_resolvable. Same for agent-tools. Dependabot does not honor { workspace = true } sources, even when declared in the root pyproject.toml.
  2. The job is right at the ~55 min timeout. Each check re-resolves the whole workspace (~16s each) and a run does 200-250 checks; ~30 of those are on workspace members, which we never want updated.

Ignoring the workspace members in .github/dependabot.yml fixes both, but an explicit list of names would have to be kept in sync manually as members are added. Options to avoid that:

Option 1: rename internal packages under a common prefix

Most members are already hackbot-*. Rename the remaining ones (agent-tools, autowebcompat-tools, bugzilla-client, lando-client, phabricator-client, phabricator-proxy, testrail-client) to e.g. hackbot-agent-tools, hackbot-testrail-client, ... so the ignore block becomes a fixed pair of wildcards:

ignore:
  - dependency-name: "hackbot-*"
  - dependency-name: "bugbug*"

Only distribution names change (pyproject.toml files and uv.lock); import names like testrail_client stay the same. It also removes a dependency-confusion risk: anything installing these outside the workspace (Docker builds, plain pip install) could currently pull an unrelated package from PyPI.

Option 2: generate the ignore list automatically

Add a pre-commit hook that reads the workspace member names and rewrites (or validates) the ignore block in dependabot.yml. No renames needed, but it adds a script to maintain and the PyPI name collisions remain.

Langage dominant
Python
Étoiles
579
Forks
369
Merge moyen
3 j 5 h
PR mergées (30 j)
139

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de mozilla/bugbug

Toutes les issues de mozilla/bugbug

Issues similaires

Plus d'issues Python

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.