Upload a folder or a build once for many leases, and put files into an app's container

Aperta
#1,636 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
20/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
android, ios, typescript

Direzione di ricerca

Read the linked request #945, lease files issue #1351, and ADR 0067 for the current upload model and its limits. The issue leaves storage scope, retention, permissions, archive unpacking, and iOS and Android container access as open design questions. Done means those behaviors are specified and a CI run can reuse one build across leases and place fixtures in each app's data container.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

feature:spec

Request: #945

Problem

A lease's files (#1351) belong to one lease, so a run that installs the same build on many leases uploads it once per lease. budgie's e2e suite (budgie-at/budgie#1867, from the comment on #945) uploads the same .app through the gateway for each of 10 leases. Requests past 100 s end in a Cloudflare 524, so it uploads at most 3 at a time, and about 4 of the run's 15 minutes are setup.

There is also no way to put files into an app's data container. budgie built a helper simulator app (E2EDrop) and sends fixtures as base64 raw-deflate on exec stdin, unpacked with simctl spawn <helper> untar <dir>.

A lease file is one flat file, and nothing unpacks an archive (ADR 0067: "Unpacking an uploaded archive into folders (an iOS .app) … not in this decision"). A simulator .app is a folder, so a remote caller cannot install an iOS app it built from the lease folder at all. #1635 (remote CLI) ships single-file uploads and leaves this here, decided in its spec session of 2026-11-17.

Who it is for

A CI run that installs one build on many leased devices, and puts test fixtures into the app on each.

Open questions

  • How a folder (an iOS .app) reaches the lease folder: simlock files put ./MyApp.app packs it and the worker unpacks it, or an archive upload is unpacked on request.
  • Where a shared upload lives (per token, per run, per gateway or worker), how long it is kept, and who may install from it.
  • How a file reaches an app's data container, on iOS and on Android.

Written by an agent.

Lingua principale
TypeScript
Stelle
705
Fork
40
Merge medio
12h 9m
PR unite (30g)
376

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di callstackincubator/simlock

Tutte le issue di callstackincubator/simlock

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.