fix(wasm): populate SelfSummary mirror fields, flag host-stats N/A, serve empty app-logs - #3639
Merged
0pcom merged 1 commit intoJul 30, 2026
Conversation
…erve empty app-logs Three surface-divergence leftovers where a healthy browser visor rendered as misconfigured/broken on the shared HV UI (the recurring "wasm mirror gap"): - SelfSummary populated only a subset of the fields the native builder fills, so a long-running tab showed "0s uptime" and autoconnect off. Now stamps a bootTime and reports real Uptime; PublicAutoconnect=true (the edge runs the WS/WebRTC autoconnect loop); IsPublic=false stated explicitly. MinHops (0) and RewardAddress (none) are the edge's honest values, left as-is. - host-stats reported 0% CPU / 0-byte RAM, indistinguishable from a real idle-but-fine host. Adds "available": false so the resources page can show N/A for a serverless visor instead of fake gauges (zeros kept for old UI). - apps/<app>/logs returned the generic subroute 404, which the Angular app-detail page turned into an error dialog. Now serves a valid empty LogsRes (200) so the logs panel renders "no logs" cleanly — the same render-cleanly-don't-404 treatment routegroups/host-stats already get. Tests: connect-all route, app-logs-not-404, and host-stats-available-false added to pkg/wasmhv/self_test.go. Wasm-only; blob re-embeds at release. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XzckVqHX624RpdEWcvVosA
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.
Three surface-divergence leftovers (the recurring wasm mirror-struct gap) where a healthy browser visor rendered as misconfigured/broken on the shared HV UI:
bootTime→ real Uptime; PublicAutoconnect=true (the edge runs the WS/WebRTC autoconnect loop); IsPublic=false stated explicitly.MinHops(0) andRewardAddress(none) are the edge's honest values.0%CPU /0-byte RAM — indistinguishable from a real idle host. Adds"available": falseso the resources page can show N/A instead of fake gauges (zeros kept for older UI).LogsRes(200) so the logs panel renders "no logs" cleanly — same render-cleanly-don't-404 treatmentroutegroups/host-statsalready get.New
pkg/wasmhv/self_test.gocases:dmsg/connect-allroute, app-logs-not-404, host-stats-available-false. Wasm-only; blob re-embeds at release.Part of the wasm-visor polish pass following the Tier A/B test harnesses (#3637, #3638).