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
{{ message }}
Repository navigation
Native private storage retirement hangs when trusted control disconnects #778
Validated against exact installed public @poe-platform/safe-bash@0.1.690, source 6256c18, during #769 consumer integration.
Unit protocol-boundary reproduction (not an actual Chromium or hosted outage claim): acquire a private storage origin lease; Target.closeTarget acknowledges success but Target.targetDestroyed has not arrived; the trusted connection reports root Inspector.detached. lease.release() remains pending and its subscription stays registered. The probe fails after a bounded 50ms observation. Current source explains the permanent missing-event case: retirement awaits a resolve-only destroyed promise and ignores control disconnection.
Required fix: make preparation and pending retirement fail explicitly on trusted whole-control disconnection, without claiming a target was destroyed or resolving successful cleanup. Preserve actual target-destruction confirmation, private-session detach behavior, target/session identity, cleanup aggregation and subscription removal. Browser owner cleanup must still delete the owned provider lease. The consumer trusted control must publish its real socket termination so the library can observe the failure; no fake Target.targetDestroyed notifications.
Add fast regression tests for global disconnect before creation/loading, disconnect after close acknowledgement while destruction is pending, and session-scoped detach during healthy native destruction. Existing actual-native/storage behavior remains required. Direct main publication and exact public verification follow the normal producer release route.
Claimed focused producer fix and fast regression coverage in home-owned detached worktree. Exact public .690 protocol-boundary probe is red: pending after trusted root Inspector.detached, with subscriber retained. This is a unit/mock transport fault—not a claimed hosted incident. Expected session-scoped detach during target destruction must remain successful; only actual trusted whole-control termination fails preparation/retirement. Consumer transport will report real EOF, never fake target destruction.
Validated fix verified on remote main at 492a3b6. Root trusted-control disconnection rejects loading/retirement and drains subscriptions without inventing target destruction; session-scoped detach remains healthy. TDD: initial five failures and additional close-response race reproduced. Integrated focused checks: 82 tests, 81 passed, zero failed, one hosted test skipped; scoped maintained ESLint clean. Release publication is being monitored separately; actual consumer EOF delivery is being tested separately.
Activity
kamilio commentedon Sep 18, 2026
Claimed focused producer fix and fast regression coverage in home-owned detached worktree. Exact public .690 protocol-boundary probe is red: pending after trusted root Inspector.detached, with subscriber retained. This is a unit/mock transport fault—not a claimed hosted incident. Expected session-scoped detach during target destruction must remain successful; only actual trusted whole-control termination fails preparation/retirement. Consumer transport will report real EOF, never fake target destruction.
fix(playwright): reject private retirement on control disconnect (#778)
kamilio commentedon Sep 18, 2026
Validated fix verified on remote main at 492a3b6. Root trusted-control disconnection rejects loading/retirement and drains subscriptions without inventing target destruction; session-scoped detach remains healthy. TDD: initial five failures and additional close-response race reproduced. Integrated focused checks: 82 tests, 81 passed, zero failed, one hosted test skipped; scoped maintained ESLint clean. Release publication is being monitored separately; actual consumer EOF delivery is being tested separately.