Skip to content

Refuse a protected launch when commit headroom is low - #10

Open
Quixyl-eng wants to merge 1 commit into
feature/exvram-controlfrom
refactor/rust-core
Open

Quixyl-eng wants to merge 1 commit into
feature/exvram-controlfrom
refactor/rust-core

Conversation

@Quixyl-eng

Copy link
Copy Markdown
Contributor

Summary

  • The language audit is in docs/LANGUAGE_MIGRATION_PLAN.md. The desktop runtime was already Rust; the Python lab stays where it is.
  • Protect My PC now refuses to start llama-server when Windows commit headroom is under 2 GiB, in addition to the existing 1.5 GiB free-RAM floor. The decision is host_pressure in the existing core. It does not kill other processes or change the pagefile.
  • CI runs cargo test for exvram-control-core.

Test plan

  • cargo test -p exvram-control-core (33 tests)
  • cargo clippy -p exvram-control-core with the pre-existing identical-branch lint allowed
  • cargo check -p exvram-control
  • ruff check src tests benchmark
  • python -m unittest discover -s tests (89 tests, 1 skipped)
  • python -m compileall -q src tests
  • Confirm Start on a machine with commit headroom under 2 GiB shows the refusal and leaves other programs running

Made with Cursor

Free RAM was already checked. Commit charge is what pushes the machine into the pagefile, and that decision now lives in the existing Rust core.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant