goon_plugin

4 Commits

Author	SHA1	Message	Date
robot	5da2003cd0	docs: draft PR description CI / test (pull_request) Successful in 5m31s Details	2026-08-31 03:27:06 +00:00
robot	97abaf42d9	feat: add user instructions to viewer popup	2026-08-31 03:26:50 +00:00
robot	c826669c7d	rename log prefixes: '[goon' -> '[vidplex' in runtime logs CI / test (pull_request) Successful in 5m34s Details	2026-08-31 01:55:27 +00:00
robot	fd8c36d72e	fix(tests): stop hls_qa deep-probe suite hanging under jsdom CI / test (pull_request) Successful in 1m56s Details CI times out on the 7 "HLS QA: Deep probe strategies" tests. Root cause is a jsdom-only artifact, not a production bug: jsdom exposes the self-referential cyclic globals (_globalObject/_globalProxy/_top/_parent/ window/self/top/parent/frames) as ENUMERABLE own-props on the window. Strategy H in m3u8DeepProbeFn() runs Object.keys(window) and a no- visited-set walk() over each, which explodes to O(204^5) ≈ 3.5e11 ops and never terminates within the depth-5 cap, so the whole suite hangs forever. A real Chrome MAIN-world window does NOT expose those keys as enumerable own-props, so this is purely a test-environment mismatch. The fix is test-only: sanitizeJsdomWinForProbe() marks the jsdom cyclic globals non-enumerable in runProbeInWin() before eval, mirroring a real page. No production/underlying source (src/viewer/index.js) is modified. Local (Node 22.22.3 / Linux == CI ubuntu-latest + Node 22): before: npm test hangs indefinitely (no Results line; CI job killed) after: npm run build && npm test -> 83/83 passed in ~12.5s	2026-08-24 05:10:56 +00:00