From 864d96e7dcb709caef253c4c549887e8afbda6fd Mon Sep 17 00:00:00 2001 From: edwinhu Date: Thu, 16 Jul 2026 15:29:21 -0400 Subject: [PATCH] paperpile: correct the wedged-tab explanation (it is not YouTube) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit a21a34d's comment says "a playing YouTube tab reproduces this", attributing the CDP hang to YouTube or to media playback. That was an over-specific inference from a single observation, and it is wrong. Re-probing the same browser three hours later: the YouTube tab that had hung reliably (twice, with and without Network.enable) now answers in milliseconds, while a wrds-www.wharton.upenn.edu tab has started hanging instead. One of six page targets hangs at any given moment, and which one drifts. It tracks renderer busyness, not the site. No code change — the fix was already right, and this makes it more clearly right: if the culprit were a known site you could skip it, but since any tab can be wedged and it moves, avoiding page targets entirely is the only sound answer. Worth correcting rather than leaving: the comment is what the next reader reasons from, and "it's the YouTube tab" invites exactly the wrong fix. Bump 5.70.1 -> 5.70.2 so this reaches the version-keyed cache — per #58, a change without a bump never ships. Verified: bash -n clean, extraction still returns 12 cookies with plack_session present. Co-Authored-By: Claude Opus 4.8 (1M context) Claude-Session: https://claude.ai/code/session_01UZvrft29zMGgks5abHVtVK --- .claude-plugin/marketplace.json | 4 ++-- .claude-plugin/plugin.json | 2 +- skills/paperpile/scripts/refresh-auth-from-dia.sh | 13 +++++++++---- 3 files changed, 12 insertions(+), 7 deletions(-) diff --git a/.claude-plugin/marketplace.json b/.claude-plugin/marketplace.json index efba9a18..64524b4c 100644 --- a/.claude-plugin/marketplace.json +++ b/.claude-plugin/marketplace.json @@ -5,14 +5,14 @@ }, "metadata": { "description": "Development, data science, and writing workflows for Claude Code", - "version": "5.70.1" + "version": "5.70.2" }, "plugins": [ { "name": "workflows", "source": "./", "description": "Unified development, data science, and writing workflows with TDD enforcement, output-first verification, GSD-style deviation rules, test gap validation, and session handoff", - "version": "5.70.1", + "version": "5.70.2", "category": "development", "tags": [ "development", diff --git a/.claude-plugin/plugin.json b/.claude-plugin/plugin.json index 0e176816..9e4f7042 100644 --- a/.claude-plugin/plugin.json +++ b/.claude-plugin/plugin.json @@ -1,6 +1,6 @@ { "name": "workflows", - "version": "5.70.1", + "version": "5.70.2", "description": "Development, data science, writing, and workshop presentation workflows with TDD enforcement, output-first verification, agent team parallelization, and GSD-style deviation rules, test gap validation, and session handoff.", "author": { "name": "edwinhu" diff --git a/skills/paperpile/scripts/refresh-auth-from-dia.sh b/skills/paperpile/scripts/refresh-auth-from-dia.sh index ce60d029..e6851380 100755 --- a/skills/paperpile/scripts/refresh-auth-from-dia.sh +++ b/skills/paperpile/scripts/refresh-auth-from-dia.sh @@ -10,10 +10,15 @@ # one command to run — there is never a reason to drive the Paperpile web UI. # # Cookies are read from the BROWSER-level CDP target via Storage.getCookies, -# not from a page target. Page targets route through a renderer, and a wedged -# tab (a playing YouTube tab reproduces this) never answers Network.getCookies — -# which used to hang this script forever, since it attached to whichever page -# happened to be listed first. The browser target has no renderer to wedge. +# not from a page target. Page targets route through a renderer, and a busy +# renderer never answers Network.getCookies — which used to hang this script +# forever, since it attached to whichever page happened to be listed first. +# +# Any tab can be the wedged one, and it moves: probing six page targets, one +# hung indefinitely while five answered in milliseconds — and three hours later +# the hung tab answered fine while a different one had started hanging. It +# tracks renderer busyness, not the site. The browser target has no renderer, +# so it cannot wedge and needs no particular tab open. set -euo pipefail PORT="${1:-9222}"