Skip to content

fix(runtime): validate engine installation completion and preserve live install state (fixes #112) - #152

Merged
BerryUIKI merged 1 commit into
devfrom
bugfix/112-validate-engine-installation-completion
Oct 4, 2026
Merged

BerryUIKI merged 1 commit into
devfrom
bugfix/112-validate-engine-installation-completion

Conversation

@BerryUIKI

Copy link
Copy Markdown
Owner

Closes #112.

Changes

  • Track active installation workers (_active_installs) in \IsolatedEngineInstaller\ so live status polling reads (
    ead_manifest) remain side-effect-free and do not erroneously mark in-progress installations as \INTERRUPTED.
  • Enforce per-engine exclusive async lease locks on \install_engine\ via \ ask_registry.get_install_lock, rejecting overlapping concurrent operations.
  • Recover and clean up corrupt or empty engine directories lacking valid entrypoints (\main.py, \launch.py/\webui.py) or .git\ before attempting repository clone.
  • Added strict post-installation validation (\�alidate_installation) verifying the hermetic Python binary, expected entrypoints, and
    equirements.txt\ before marking \COMPLETED.
  • Added regression tests in \ est_m2_engines.py\ verifying live polling stability, empty directory/missing entrypoint rejection, and per-engine lease locking.

@BerryUIKI
BerryUIKI merged commit 223a0ba into dev Oct 4, 2026
3 checks passed
@BerryUIKI
BerryUIKI deleted the bugfix/112-validate-engine-installation-completion branch October 5, 2026 19:04
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