Skip to content

v0.4.4: never echo a malformed proxy line; stop pyppeteer proxy auth before close - #10

Merged
chakh1ik merged 1 commit into
mainfrom
fix/pyppeteer-close-and-proxy-echo
Oct 19, 2026
Merged

chakh1ik merged 1 commit into
mainfrom
fix/pyppeteer-close-and-proxy-echo

Conversation

@chakh1ik

Copy link
Copy Markdown
Collaborator

Two fixes ported from the tipranks-scraper live test pass (2scraper/tipranks-scraper#6).

  • proxy_pool.parse_proxy_line: a malformed line was echoed in ProxyParseError (unrecognised proxy format: 'http://user:pass@…'), which can expose its password. The message now lists the accepted formats instead.
  • pyppeteer sends Fetch.disable before both browser.close() paths when proxy auth is on. In tipranks a paused request answered while the target closed left an unretrieved "Target closed" error on stderr. Here it was not seen, but the timing is the same.

Verified

  • smoke_test.py: 81/81 in every engine venv and with no engine installed (two new checks).
  • Live: two pyppeteer runs through an authenticated HTTP proxy, 10 rows each, no "Target closed" output. A malformed --proxy exits 2 and the password is not in the message.

🤖 Generated with Claude Code

…before close

Ported from tipranks-scraper's live test pass.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
@chakh1ik
chakh1ik merged commit dc50eef into main Oct 19, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant