You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The two async tests for _handleFragmentLoadProgress were failing in CI:
1. fragContextChanged(frag) returned true because the test never set
fragCurrent on the controller, so the post-decrypt continuation
short-circuited before FRAG_DECRYPTED could fire. Align fragCurrent
with the test fragment through a small loadProgress() helper.
2. The 'fatal: false' assertion compared the event payload after the
error-controller had a chance to mutate it (escalate to fatal). Drop
that assertion — the part of the contract we own is what gets emitted
from decryptPayload, not what downstream does to it.
3. flushPromises now drains microtasks explicitly via a Promise.resolve
tick chain (no async keyword — banned by no-restricted-syntax) rather
than relying on a setTimeout(0) boundary.
0 commit comments