A challenge's backoff no longer refuses the solver read that follows it #82
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/solver-after-challenge"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Makes #78's fix work in production. OpenSpec change:
solver-after-challenge.The bug
The app's browser meets a challenge on a player page, and
courtesy.record(challenge=True)backs the host off.solver.fetch_page, the next step of the same read, is then refused by that backoff and returns None. So the solver fallback for challenged player pages has not been running on any site, and PR #81's player frames were never reached. PR #81's tests replaced the solver and page read with stand-ins, which hid it.The fix
solver.fetch_page(after_challenge=True)goes past the backoff (courtesy.acquire(past_backoff=True)), and a page coming back doesn't end it._read_player_pageends the backoff when the read finds a stream. A read that finds none keeps it, and it doubles as before, so a dead end like tvsportslive.fr is still left alone longer each time.Checks
dudestream1.com): read OK in 35 s through the solver and thestreamec.stframe. An earlier run this session, with the backoff cleared by hand, passed the app's verify at 1280×720, 30 fps.make test: 872 passed, 1 skipped. One earlier run took 137 s and failedtest_the_lifespan_writes_the_snapshot_before_its_other_shutdown_work. That didn't reproduce: it passes alone and the next full run took 16 s.Worth watching after deploy: gated sites now get a solver read as designed, so solver use on those hosts goes up. A read of such a link takes about 35 s, not 20 s.
🤖 Generated with Claude Code