Add native production smoke checks#72
Open
sonukapoor wants to merge 1 commit into
Open
Conversation
Open
sonukapoor
force-pushed
the
production-readiness-validation
branch
from
da35ff9 to
6438b2c
Compare
sonukapoor
changed the title
sonukapoor
force-pushed
the
production-readiness-validation
branch
from
6438b2c to
a1dc054
Compare
Contributor
Author
|
@syrusakbary CI is green now after the unrelated WASIX smoke instability was fixed across the open branches. This PR is scoped to a small native production-readiness smoke set for the 0.x roadmap. If the scope looks aligned, I think it is ready for review. |
rbbydotdev
added a commit
to rbbydotdev/edgejs
that referenced
this pull request
Jun 22, 2026
…sign) → pinpointed the real blocker Bus-based probes (entry heartbeat posts RC/DRAW/ANSI via the BroadcastChannel, harness collects window.__probes) proved: the entry's heartbeat setInterval NEVER fires after the server boot, while CDP caught worker.ts's setInterval firing fine. So opentui's timer-driven render loop never ticks in the entry/bundle's contextify vm-context env → only the clear escape (7B) reaches ghostty, no content frames. The worker is HEALTHY (not blocked) and the bundle IMPORTS + server LISTENS — the wall is now a precise edge jsloop timer-draining / run-env issue (wasmerio#71/wasmerio#72 family), NOT opentui or the App. Adapter probes stripped after the finding.
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
1 participant
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.
This turns part of the 0.x production-readiness roadmap from #8 into a small native smoke path. It is not a production-readiness gate or release sign-off; it gives future readiness work a repeatable starting point for basic runtime checks.
The PR adds
make test-production-readiness, a shell runner, two native fixtures, and a short roadmap doc. The first smoke set covers the version path, eval path, built-in module loading, HTTP loopback lifecycle, and repeated cold starts. Each case has a timeout so a stuck runtime invocation fails the smoke run instead of hanging indefinitely.Safe-mode smoke remains optional with
EDGE_PRODUCTION_READINESS_SAFE=1, and network/TLS safe-mode coverage stays on the existingmake test-wasix-safe-modepath.I verified this locally with:
The local native smoke run passed 5 checks with 0 failures.