what the title says. I activate in-flight mode, do stuff, exit the app and restart it, and in-flight mode is disabled again. in-flight mode must persist over restarts.
what the title says. I activate in-flight mode, do stuff, exit the app and restart it, and in-flight mode is disabled again. in-flight mode must persist over restarts.
hugo
added the bug label 2026-07-20 18:59:50 +00:00
Implemented in 557497d and pushed to origin/main. The status-bar airplane switch now persists through the shared settings engine under the bDS2-compatible ai.airplane_mode_enabled key, is restored during desktop startup, defaults safely to airplane mode when unset, and changes UI/model routing only after the database write succeeds. Persistence failures retain the prior mode and produce a localized error. Coverage includes real SQLite close/reopen in both directions plus desktop hydration and status-bar update persistence. Verification: targeted red/green tests, cargo fmt --check, cargo clippy --workspace --all-targets -- -D warnings, cargo build --workspace, cargo test --workspace (bds-core 481 passed/1 ignored; bds-ui 170 passed; all remaining integration and doc tests passed), git diff --check, allium check specs, and allium analyse specs. A neutral comparison against issue #64, bDS2 AI.set_airplane_mode/airplane_mode? and ShellLive mount behavior, and the Allium status-bar/airplane-routing invariants found no remaining gap.
Implemented in 557497d and pushed to origin/main. The status-bar airplane switch now persists through the shared settings engine under the bDS2-compatible ai.airplane_mode_enabled key, is restored during desktop startup, defaults safely to airplane mode when unset, and changes UI/model routing only after the database write succeeds. Persistence failures retain the prior mode and produce a localized error. Coverage includes real SQLite close/reopen in both directions plus desktop hydration and status-bar update persistence. Verification: targeted red/green tests, cargo fmt --check, cargo clippy --workspace --all-targets -- -D warnings, cargo build --workspace, cargo test --workspace (bds-core 481 passed/1 ignored; bds-ui 170 passed; all remaining integration and doc tests passed), git diff --check, allium check specs, and allium analyse specs. A neutral comparison against issue #64, bDS2 AI.set_airplane_mode/airplane_mode? and ShellLive mount behavior, and the Allium status-bar/airplane-routing invariants found no remaining gap.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
what the title says. I activate in-flight mode, do stuff, exit the app and restart it, and in-flight mode is disabled again. in-flight mode must persist over restarts.
Implemented in
557497dand pushed to origin/main. The status-bar airplane switch now persists through the shared settings engine under the bDS2-compatible ai.airplane_mode_enabled key, is restored during desktop startup, defaults safely to airplane mode when unset, and changes UI/model routing only after the database write succeeds. Persistence failures retain the prior mode and produce a localized error. Coverage includes real SQLite close/reopen in both directions plus desktop hydration and status-bar update persistence. Verification: targeted red/green tests, cargo fmt --check, cargo clippy --workspace --all-targets -- -D warnings, cargo build --workspace, cargo test --workspace (bds-core 481 passed/1 ignored; bds-ui 170 passed; all remaining integration and doc tests passed), git diff --check, allium check specs, and allium analyse specs. A neutral comparison against issue #64, bDS2 AI.set_airplane_mode/airplane_mode? and ShellLive mount behavior, and the Allium status-bar/airplane-routing invariants found no remaining gap.