bootc-dev / bootc-dev/bootc

Bootc status without sysroot lock

Aperta
#585 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub
area/client bug enhancement
Lingua principale
Rust
Stelle
2.3k
Fork
230
Merge medio
3g 12h
PR unite (30g)
38

Descrizione

When an automated upgrade is happening in the background, you are unable to query `bootc status` to see information about the current deployment (or to see the upgrade is in progress), since status requires a sysroot lock. I would expect such read-only commands (I can only think of status for now) to not require a system lock, and display the regular output regardless of whether another process is happening.

This could cause some confusion when you're blocked from seeing information about your system due to a command that's invoked without the user saying to do so.

If there's some context I am missing or a technical limitation, I'm more than happy for you to say "this is expected" and close this.

Guida per i contributori

Apri la guida per i contributori

Direzione di ricerca

Start by locating the `bootc status` command and where it acquires the sysroot lock, then inspect any existing status or locking tests. Done means read-only status output remains available while an automated upgrade holds the lock, with regression coverage for that situation.

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

Valutazione

Stack tecnologico
rust
Ambito
cli, operating-systems
Tipo di issue
Bug
Difficoltà
4/5
Tempo stimato
3-5 giorni
Stato di attività
Ferma
Chiarezza
Abbastanza chiara
Idoneità per principianti
42/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.