Repository navigation
Release/v1.3.0 - #15
Merged
Merged
Conversation
…sions; accounts listing; concurrency over CDP refused - --out into a missing directory: the writer creates it (was exit 1 after scraping) - market-values: a gallery-shaped next-link is ignored, ?page=N fetched (404 ended 3 of 8 runs at page 1) - --concurrency: an unserved page past the listing's end no longer makes a complete run partial - --proxy-sessions accepts .proxy.rucaptcha.com - accounts: one row per account with proxyMode - --concurrency over --cdp-endpoint: exit 2, as the README says - CDP connect hint follows the error; diff_runs advice follows the reason - README / TROUBLESHOOTING / CHANGELOG updated Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…eout, proxy_error); hint names it Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
… per host), generated and checked against measured pairs Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…mes it current) Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…on the profile's exit; voucher exchanged; pyppeteer loop drained Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Both had been guessed as "th." and "k" and never measured, so every value under EUR 1m on .co.kr and .jp came out as price null. Measured 2026-10-25 on Bayern's squad; 23 of 23 rows priced live on both hosts. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Met 2026-10-25 on one of three parallel connects (HTTP 500, body "fingerprint_error"); the same profile connected a minute later. It was not retried, and the hint blamed a busy pid or a failed exit. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…eteer proxy auth and auto-solve A browser never says a proxy refused its login. Measured 2026-10-25 with a bogus login on the real gateway: Playwright waited out the load timeout (60 s an attempt, page_load_timeout) and Selenium read Chrome's error page as zero rows (exit 4). Every engine now sends one CONNECT per exit before its first page; a 407 is stop_reason proxy_auth_refused, exit 5, in 1-2 s, with nothing requested from the site. pyppeteer's page.authenticate() needs Network.setRequestInterception, gone from current Chrome: every run with a proxy login died before the first page. The challenge is now answered over the CDP Fetch domain. And Captcha.setAutoSolve was handed to the loop bridge as a Future, so it raised on every connect and was logged as "not available": the Scraping Browser's auto-solve was never on for pyppeteer. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.