Repository navigation
Conversation
Set up imports the distro and returns while it is stopped. The next Install click is the first command into that distro. These tests fail while that command is still the 20 second tool check. Co-authored-by: Cursor <cursoragent@cursor.com>
The 3 minute wait ran only when Install itself imported the distro. Set up imports first, so Install saw a listed distro and used the 20 second tool check for the first boot. CI run 42237456986 failed 20.3 seconds after that click. Co-authored-by: Cursor <cursoragent@cursor.com>
The wait, the 20 second tool check, and the test already show the order. A second copy of that fact in a comment is not needed. Co-authored-by: Cursor <cursoragent@cursor.com>
The Jetson uses glibc 2.35, and the bundled fpm binary is x86. Co-authored-by: Cursor <cursoragent@cursor.com>
Keep the Ubuntu 22.04 arm64 jobs, and poll Linux status from Node so the page CSP allows the check. Co-authored-by: Cursor <cursoragent@cursor.com>
Version 26.16.1 already downloads fpm-1.17.0-ruby-3.4.3-linux-arm64v8, so the system fpm install is obsolete. Co-authored-by: Cursor <cursoragent@cursor.com>
The Windows Install job reached Open my computer and /healthz. It did not click Open Home, Stop, Start, or the update check. Co-authored-by: Cursor <cursoragent@cursor.com>
…is absent. Co-authored-by: Cursor <cursoragent@cursor.com>
Runtime 2.0.0 does not write update-check.json. The Mac branch derives that record from the signed head. Windows now writes the same record inside the distro. Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
…us file is absent." This reverts commit bb7d4b6.
Windows Update stays one command. The Linux test fails until that restart lands. Co-authored-by: Cursor <cursoragent@cursor.com>
A closed window leaves Home and the tray. Update and Undo stop Home, run the command, and start Home again. Co-authored-by: Cursor <cursoragent@cursor.com>
The update controller does not hold the listen socket. Its child does. Co-authored-by: Cursor <cursoragent@cursor.com>
elastos gateway never enters the update controller, so System update inside Home cannot run on Windows. Start home --browser, signal the proved controller on Stop, and start Home again after Update and Undo. Co-authored-by: Cursor <cursoragent@cursor.com>
This was referenced Nov 8, 2026
A tag build is a release: it must notarize and fail closed. Test builds (dispatch without the notarize input) still skip Apple. Drops a test that pinned the workflow expression text.
Matches the platform names (Login Items, Startup apps) and Docker Desktop's wording, avoids 'sign in' (Home passkey sign-in), and says Home keeps running when the window is closed.
… drag start Run 42501403861: the e2e read #logs-content with innerText, which is empty while Details is closed (install had reached Open Home); textContent reads it. The top-strip drag moved the window 60 x 35 for a 60 x 45 OS drag, because macOS starts dragging after a few points; assert real movement instead of an exact delta.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
592bb51293ad553e82ab73c9b4d65f7cd7fe869c: runtimeUpdate.ts:86, runtimeGateway.ts:353, runtimeGateway.ts:852, and runtimeTarget.ts:127. Also read original elastos-runtime #486 and the pinned Runtime v2.0.0 controller source.The Mac launcher follows signed Runtime releases on the selected channel with a 2.0.0 floor, adopts an independently proved installed Home, and keeps lifecycle requests ordered.
verifiedHeadForRollbackfor both Restore and the CID saved before Update. Signed 1.9.9 heads cause no restore/update mutation.home --browserowns gateway-child restarts; the launcher waits for an explicit Start after controller exit.install_path, including a different basename or symlink. A bundled 24-line Mac helper usesproc_pidpathandproc_pidinfoto supply the executable and precise birth time; both are rechecked before TERM/KILL. Bound lock/status reads and bind controller adoption to the host generation and parent. A stale controller record grants no authority over that controller; Stop can still use the separately proved orphaned host. Writeprevious-head.jsonwith a temporary file, fsync and rename.~/.elastos-launcher/electron, preserve Runtime's own update decisions with a launcher-owned signed fallback when missing, and keep explicit control of Home when closing the window or quitting.Validation for
66d8dd0ebc64da2ee368b82c0734883d9edc98f5:elastos-heavy npm test: 293 tests, 290 passed, 0 failed, 3 platform skips.Focused fail-before/pass-after evidence from
test/runtime-round4.test.js(same test source, real compiled consumers):The Mac Electron scenario kills its own spawned controller, requires Error, stops any retained proved Home, and explicitly starts a healthy Home again. It also gracefully terminates its adopted controller, requires Stopped and unhealthy Home, then explicitly starts Home. Existing install, Open, window close, Update, adoption, Quit, foreign-listener and packaged-profile checks remain.
The initial CI Test failure exposed a Mac fixture using the x64 runner's default architecture. Both Mac fixture calls now pass
arm64; a simulated x64 host replay passes all 15 update cases. Native testing also showed thatps commis spoofable; the final executable identity useslibproc. A positive test against a hardened fixture in a private directory exposedvmmappath redaction; its identical fail-before/pass-after replay against the vmmap implementation is retained. The helper targets macOS 11 explicitly, with both Mach-O headers checked, and the package verifier executes the actual unpacked helper before any packaged launch. These and other reproduced findings were recorded in the failure ledger (1216–1221, 1223–1227, 1229–1230, 1232–1233, 1232–1233).Premortem passed with the actual PR base. Checked explicit host inputs, real-module fixtures, complete test/caller coverage, both version-floor paths and every signal stage, and secret output. The default premortem cannot resolve
origin/develophere, and the two elastos-runtime shell gate scripts do not exist in this launcher repository; both were attempted and are not passed. The rented Rust full check does not apply to this Node/Electron branch, which is not pushed to develop.Linux spawn arguments, index.ts Linux window handling and windowsRuntime.ts are unchanged from
592bb51. The round-3 DMG remains untouched at SHA-2569a44f80920955223145b49cbb5107319e8c43ac69e0141ddddb5b74d598c4ed2. The new DMG, SHA-256 file and full per-test verification report are in~/omp-inbox/launcher/next/. SHA-256:528bb08032ead6ce32f0766e09bf28239e5b16fde229511afb2a025a01e802ff. The delivered app passed image checksum verification, deep/strict code-signature verification, packaged native-helper execution, both macOS 11 architecture headers and the guarded local loader-only check. Full packaged launches ran only on the GitHub runner. A real signed Stable upgrade to a newer version remains unavailable; same-version Update and signed verification are exercised. This PR stays draft. No merge, tag or release.Final Mac runner evidence:
The retained-orphan path is covered by the direct adoption regression; this live crash run observed Home already stopped. Test and all nine smoke jobs checked out
b85f3586599f8686a296e1e04f511861b0f08104, whose tree equals head66d8dd0(parents include that head). Full local per-test fail/pass lines, all check results and failure-ledger records are in the verification report. No ready/merge/tag/release action was taken.