Repository navigation
avito-scraper v1.1.2 - #10
Merged
Merged
Conversation
…pt sidecar; accounts lists accounts only From the 2026-10-19 manual test of v1.1.1: - env_config.py printed AVITO_PROXY in host:port:login:password form whole - latest_attempt sidecar carried exit_code only on transport failures - diff_runs compared a full run with a --max-products-capped one - browser_profile_client accounts mixed accounts, profiles and proxy accounts - proof-of-work log said "cleared" for a page still loading; stop line quoted the first response's status - "not a item page"; proxy-login hint named one gateway host - .gitignore matched --dump-html captures by extension, not by shape - secret scan exempted smoke_test.py; citation check walked ignored files - README GeeTest table carries the 0-of-9 local measurements and the 2026-10-14 proxy control; seller mode and "removed" explained Each fix has a check that fails on c97fb8c. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
…al advice follows the reason - fetch_page passed the wall rungs before its second wait, so a captcha that surfaced during that wait was never solved and the run rotated to a fresh exit (2026-10-19, step 42: twice in three exits). The rungs now run once more after that wait. - diff_runs advised "re-run the incomplete side" for every refusal, including two complete runs capped differently; advice now per reason. Both checks fail on 8eb7749. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
… canary endpoint as a tool with one retry - a transport failure after gathered pages was exit 5 with the rows thrown away (live, pyppeteer, 2026-10-20); it is now a partial run, exit 6 - `500 profile_locked` at connect is retried 3x10 s; timeouts and proxy_error are not - pyppeteer's bare TimeoutError on a refused CDP connect now names what it may hide and where to see the reason - canary.yml: the inline Python heredoc is `browser_profile_client.py canary-env`; a live run that exits 5 is retried once on a fresh session - README/CHANGELOG: local-route GeeTest refusals 0 of 14 (2026-10-14..20) Each change has a check that fails on 6f615bf. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
…exit 5/6 and canary retry described Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
…a fault after gathered rows Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
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.