chore: refresh data with new entries till 30.9.25 and backfill #63
Conversation
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
anxkhn
force-pushed
the
sept-data-refresh
branch
from
55233ae to
7379ce6
Compare
anxkhn
changed the title
anxkhn
changed the title
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR updates the dataset as of 2025-09-09 using the new Selenium-based extraction method (introduced because LeetCode changed their GraphQL API and no longer provides full content via the
ugcArticleDiscussionArticlesquery).While fetching data, the scraper currently used
max_recs = 2000, which caps the number of posts fetched.However this begs an interesting question:
Is there a reason we limit to 2000?
We’re losing all older entries, this is intended behavior, but any reason why?
I am in favor of creating a fork which stores all the data, even beyond 2000.