Dependabot uv job times out and tries to update workspace members

Aberta
#7,457 2 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 3 dias

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
45/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
github-actions, python, yaml
Domínio
build-system, devops

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
Python
Estrelas
579
Forks
369
Merge médio
3d 5h
PRs com merge (30d)
139

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de mozilla/bugbug

Todas as issues de mozilla/bugbug

Issues semelhantes

Mais issues de Python

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.