iOS: destroy stops at a timed-out simctl shutdown, so quarantine never reaches simctl delete

Abierto
#1,803 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
30/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
ios, typescript
Área
devtools

Línea de trabajo

Start in src/drivers/ios/simctl.ts around line 64, where shutdown uses COMMAND_TIMEOUT_MS, then read destroy in src/drivers/ios/index.ts near lines 449-452. The retry and give-up calls are in src/core/quarantine-coordinator.ts at lines 313 and 367. The open question is whether simctl delete succeeds while a shutdown is unfinished; answer it on a real simulator before changing the code. Done means a timed-out shutdown no longer blocks the delete, or a setting exists for the shutdown timeout.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug:new

A simulator whose simctl shutdown keeps running past 30 s is never deleted at lease end, in quarantine or at give-up, because the iOS destroy stops at the shutdown.

  • src/drivers/ios/simctl.ts:64: shutdown waits a fixed COMMAND_TIMEOUT_MS (30 s), and throws simctl shutdown <udid> timed out after 30000ms at the limit. No setting changes it (#1563 added ios.simulator.createTimeoutMs for clone/create only).
  • src/drivers/ios/index.ts:449-452: destroy runs shutdown and then simctl delete. A shutdown that times out throws before delete is tried.
  • src/core/quarantine-coordinator.ts:313 (each retry) and :367 (give-up) both call that destroy. On a host where the shutdown keeps timing out (memory pressure, swap ~2.5 GB in #1801), each attempt spends 30 s on the shutdown and none reaches the delete. The device ends device.quarantine-stranded, keeping its capacity slot and its disk until an operator acts.

The record is kept, so this leaves no orphan. #1801 showed the log lines but not this end state.

Open question for the fix, to settle on a real simulator: does simctl delete remove a simulator whose shutdown has not finished? If it does, destroy can go on to the delete after a timed-out shutdown. If not, the shutdown needs a setting like createTimeoutMs.

Found while triaging #1801.

Written by an agent.

Lenguaje dominante
TypeScript
Estrellas
705
Forks
40
Merge medio
12 h 9 min
PR fusionados (30 d)
376

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de callstackincubator/simlock

Todos los issues de callstackincubator/simlock

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.