Repository navigation
Carry this run's trail in the NUI report, read back from disk (issue 100) - #125
Merged
Merged
Conversation
…100) The page FUSIONOF sent on 2026-10-04, fetched while TikTok was on screen refusing every video, carried the header's one-line snapshot of each probe (media: 0x0 rs0 starved stuck, mse format: one avc1 init segment) and not one line of the sequence behind it. The NUI report had the previous run's trail and this run's DiagLog, and every media:, mse:, hold: and page error: line is trail-only by design, so the evidence the reporter was asked for twice was on disk and on no page. Breadcrumbs.Current reads this run's file back on the diagnostics server's thread, shared for writing, the last megabyte past the cap, and the NUI report carries it as "this run (the trail so far)", with trail write: in its header as the ElmSharp report already has. The trail harness holds the read-back. INTERNALS reads the page: the proxy that refused every load the day before now starves video, no element error, nothing of ours refused, and what decides it needs no build.
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.
The page FUSIONOF sent on 2026-10-04 on #100 (TikTok refusing every video with its own "trouble playing this video" toast) was fetched while the app was open, exactly as asked, and it carried the header's one-line snapshot of each probe and not one line of the sequence behind it. The NUI report had the previous run's trail and this run's
DiagLog; everymedia:,mse:,hold:andpage error:line is trail-only by design, so the evidence was on disk and on no page. INTERNALS had said thethis runblock carries it. It never did, on either build.Breadcrumbs.Current: this run's trail file read back on the diagnostics server's thread, shared for writing, the last megabyte when it has grown past that, with the cut said out loud.this run (the trail so far)ahead ofprevious run, and gains thetrail write:header line the ElmSharp report already has.tools/trail/run.shholds the read-back: trail-only lines present, a later line picked up, the cap honoured from the end.rs0, no element error, nothing of ours refused, hold switched off by the menu row), corrects thethis runclaim, and names what decides it. CLAUDE.md says what each build'sthis runis.Nothing in the app's behaviour changes. The ewk packages compile the accessor and never call it.
./build.sh allclean,tools/trail/run.shpasses.