Repository navigation
Conversation
Mantisus
force-pushed
the
keep-state-across-runs
branch
from
November 15, 2026 22:39
e3dc508 to
41411cc
Compare
This branch has not been deployed
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.
Description
run()continues the crawl: it adds to the statistics of the earlier runs, error trackers included, and keeps the sessions of the session pool.max_requests_per_crawlcounts the requests of the earlier runs too, so a run that starts with the limit already reached stops right away. To count from zero, callcrawler.statistics.reset()before the nextrun().run()continues the queue but resets the statistics the crawler built crawlee#4397.Issues
Testing
✍️ Drafted by Claude Code