Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Flake: sbt 1.2.8 warm-cache `update` in Dockerfile.sbt hangs until the 45-min job timeout

Aberta
  • Algo errado?
#1,665 5 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
3/5
Tempo estimado
1-2 dias
Facilidade para iniciantes
55/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
docker, github-actions, scala
Domínio
build-system, ci-cd

Direção de pesquisa

Start by reading tests/docker/Dockerfile.sbt and the workflow jobs coverage-docker (sbt) and e2e-docker (sbt); compare their warm-cache sbt update step with the successful nightly runs. On a workflow dispatch, enable the suggested sbt debug logging to identify whether resolver access stalls before choosing a timeout or retry. Done means the warm-cache build finishes reliably and a stalled resolver fails within a bounded time with useful diagnostics.

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

Descrição

agent:triaged ci-janitor priority:p3

docker build of tests/docker/Dockerfile.sbt hung in its warm-cache layer three times in about 90 minutes this morning (2026-10-22). Each time the job sat until its 45-min timeout-minutes killed it.

Run / attempt Job Runner Hung step Duration
39745825228 #1 coverage-docker (sbt) depot-5chxnxdgmt Build sbt image 08:17 → 09:02 (cancelled by timeout)
39745825228 #1 e2e-docker (sbt) depot-0xcx81brcg Build sbt image 08:17 → 09:02 (cancelled by timeout)
39745825228 #2 e2e-docker (sbt) depot-bdcmbfmvlt Build sbt image 09:02 → 45-min timeout

In the attempt-1 coverage-docker (sbt) log the sbt launcher fetches sbt 1.2.8 and Scala 2.12.7 in ~3 s. Then it prints nothing for 44 min:

#17 3.628 [info] Loading project definition from /tmp/warm-1.2.8/project
#17 3.709 [info] Updating ProjectRef(uri("file:/tmp/warm-1.2.8/project/"), "warm-1-2-8-build")...
2026-10-22T09:01:59Z ##[error]Step canceled by GitHub

The usual time for the whole job is ~6 min (nightly e2e-docker (sbt) on 10-19 and 10-21).

Impact: schedule and workflow_dispatch only (coverage-docker / e2e-docker); sbt-compatibility.yml has not run since 10-09. Not merge-blocking today. But each hang burns 45 runner-min per sbt leg and turns the nightly red with no diagnostic.

Likely cause (unconfirmed): sbt 1.2.8 resolves its build definition through Ivy, which has no socket read timeout. One stalled connection to a resolver (Maven Central, repo.scala-sbt.org, repo.typesafe.com) then hangs update forever instead of failing. The same layer's curl downloads all have --retry; this step has neither a retry nor a deadline.

Candidate fix for a future janitor run:

  • Pass JVM socket timeouts (-Dsun.net.client.defaultConnectTimeout / -Dsun.net.client.defaultReadTimeout) to the warm sbt update calls, so a stalled resolver fails fast and the layer can retry once.
  • First confirm which host stalls: run with -Dsbt.log.noformat=true -debug on a dispatch.

Generated by Claude Code

Linguagem predominante
Rust
Estrelas
8
Forks
2
Merge médio
19h 47min
PRs com merge (30d)
662

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 SocketDev/socket-patch

Todas as issues de SocketDev/socket-patch

Issues semelhantes

Mais issues de Rust

Receba novas issues na sua caixa de entrada

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