Save a baseline from a shut-down simulator Simlock did not make
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 18/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- ios, macos, sqlite, typescript
- Ambito
- devtools, testing-qa
Direzione di ricerca
The request is a new simlock baseline import command that copies an existing Shutdown simulator from Xcode's default device set into a baseline, so the work spans the baseline save path, lease creation and the path rewrite before first boot. Start from the existing baseline save implementation and the code that writes baseline.saved events, then read how a lease copies stored paths. Done means the refusals happen before copying, the original is never booted or changed, and the UDID rewrite keeps file lengths. The author offered to open a pull request, so check with maintainers before starting.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
The problem
A baseline can only be saved from a simulator Simlock leased (simlock baseline save <name> --lease <id>). Some state can only be prepared by hand on a simulator someone already has: for example an app signed in through a provider that needs a person (Sign in with Apple, a passkey, a second factor), with the app's keychain items and data in place. That simulator lives in Xcode's device set and was not made by Simlock, so there is no way to give agents copies of it. Doing the same sign-in again inside a lease is not possible without the person, and has to be repeated whenever the state should be refreshed.
Who runs into this
Coding agents that check an app's signed-in screens against a real account. A person signs in once on a simulator they keep; agents should each get a disposable copy, and the original must never be booted, changed or deleted by the tool.
What you would like to happen
A command that saves a baseline from an existing simulator, for example:
simlock baseline import <name> --device <udid> [--mode slim|full] [--note <text>]
- The simulator must be in Xcode's device set (with
drivers.ios.deviceSet: "default"),Shutdown, and not made by Simlock; anything else is refused before anything is copied. - Simlock only reads it:
simctl cloneinto the sources set, and nothing that boots, shuts down, erases, renames or marks it. A simulator that is no longerShutdownafter the copy has its copy dropped. - The baseline is the next version of the name, as a save is, and
baseline.savedannounces it (with the device in place of the lease). - A lease of it gets the simulator's model and OS version and the requested mode, and is deleted on release as any lease is.
- Before a lease's copy first boots, the original simulator's UDID in the copy's stored paths (text in UTF-8 and UTF-16LE, and link targets) is replaced with the copy's own, and SQLite write-ahead logs it rewrote are sealed again. Without that, a booted copy's daemons write into the original simulator, which still exists. The original and the copy are both in Xcode's device set, so the UDID is the only part of the paths that differs, and the swap keeps every file's length.
To pick up later changes to the original, shut it down and import it again under the same name.
Anything else
I have this built and tested against 0.7.0 (unit tests for the import, the refusals, the copy rewrite and the write-ahead log; used live with a signed-in simulator) and can open a pull request if it is welcome. Related: #1548, where every copy of a seed writes into the seed for the same reason (stored paths), which the UDID swap alone cannot fix because a seed and its copies live in different folders.
- 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
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di callstackincubator/simlock
-
request:new
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
callstackincubator/simlock#1806 ·
I maintainer di solito rispondono entro 1 giorno
-
bug:new
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
callstackincubator/simlock#1780 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
task:draft
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
callstackincubator/simlock#1441 ·
I maintainer di solito rispondono entro 1 giorno
-
bug:new
Difficoltà 2/5 1-3 ore Idoneità per principianti 45/100
callstackincubator/simlock#1805 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
bug:new
Difficoltà 2/5 1-3 ore Idoneità per principianti 45/100
callstackincubator/simlock#1804 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di callstackincubator/simlock
Issue simili
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 82/100
I maintainer di solito rispondono entro 1 giorno
-
Update project links after the repository renamesForse già presa @JonathanTSilva l’ha presa oggi. Apertaai-generated priority: p2 size: xs type: bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
JonathanTSilva/jts-website#119 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 74/100
promplate/code-review#158 · 1 commento · 1 reazione ·
I maintainer di solito rispondono entro 1 giorno
-
[Docs] CONTRIBUTING points the Backend Remake milestone at a branch that does not existForse già presa @franpts2 l’ha presa oggi. Apertadocs
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 90/100
I maintainer di solito rispondono entro 3 giorni