run-task hangs when cloning a github repository with LFS files and git-lfs installed
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 35/100
Línea de trabajo
Start at the run-task entry point that invokes the GitHub clone command, and inspect how its standard input and process termination are handled. Reproduce the credential-prompt scenario with a repository containing LFS files, then verify that the task aborts instead of waiting until timeout.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
We had an odd issue in some translations tasks last week: they suddenly started requiring credentials to clone the repository. It's unclear why this happened (the repository is still public...), but nevertheless it highlighted the fact that run-task simply hangs in this scenario, and wastes resources until the task times out:
[vcs 2025-09-09T18:43:02.107+00:00] executing ['git', 'clone', 'https://github.com/mozilla/translations', '/builds/worker/checkouts/vcs']
[vcs 2025-09-09T18:43:02.109+00:00] Cloning into '/builds/worker/checkouts/vcs'...
Username for 'https://github.com': [taskcluster 2025-09-09T18:59:21.223Z] [taskcluster-proxy] Successfully refreshed taskcluster-proxy credentials: task-client/Mir70a0hRim0qvIfTjAcRw/0/on/us-west1-b/3099223815166478912/until/1757445561.163
[taskcluster 2025-09-09T19:16:21.206Z] [taskcluster-proxy] Successfully refreshed taskcluster-proxy credentials: task-client/Mir70a0hRim0qvIfTjAcRw/0/on/us-west1-b/3099223815166478912/until/1757446581.188
...
...
...
[taskcluster 2025-09-15T10:08:41.854Z] Command ABORTED after 135h25m43.489856784s: process aborted
[taskcluster 2025-09-15T10:08:41.854Z] Average Available System Memory: 49.86 GiB
[taskcluster 2025-09-15T10:08:41.854Z] Average System Memory Used: 568.96 MiB
[taskcluster 2025-09-15T10:08:41.854Z] Peak System Memory Used: 886.15 MiB
[taskcluster 2025-09-15T10:08:41.854Z] Total System Memory: 50.98 GiB
[taskcluster 2025-09-15T10:08:41.854Z]
[taskcluster 2025-09-15T10:08:41.866Z] === Task Finished ===
We should find a way to detect this and abort.
- Lenguaje dominante
- Python
- Estrellas
- 26
- Forks
- 55
- Merge medio
- 2 d 6 min
- PR fusionados (30 d)
- 15
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de taskcluster/taskgraph
-
Dependency Dashboard Abierto
Dificultad 5/5 Más de una semana Aptitud para principiantes 20/100
taskcluster/taskgraph#952 ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
taskcluster/taskgraph#915 ·
-
feature
Dificultad 3/5 1-2 días Aptitud para principiantes 35/100
taskcluster/taskgraph#911 · 1 comentario ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 45/100
taskcluster/taskgraph#882 ·
-
Further optimize Git clones Abierto
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
taskcluster/taskgraph#865 · 1 comentario ·
Todos los issues de taskcluster/taskgraph
Issues similares
-
essnmx good first issue
Dificultad 1/5 Menos de una hora Aptitud para principiantes 95/100
-
[Feature] 奇物选择添加优先级 Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
syfoud/Simulated_Scepter#174 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
Giskard-AI/giskard-oss#2840 · 1 comentario ·
-
A claim comment carrying the issue number is silently declined while the workflow reports success Abiertoarea: repo bug perceived difficulty: 2
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
yeti-platform/yeti#1380 ·