fix: resolve Cloudflare fetch issues and add daily challenge auto-scraping - #7
Open
l1ve709 wants to merge 4 commits into
Open
fix: resolve Cloudflare fetch issues and add daily challenge auto-scraping#7l1ve709 wants to merge 4 commits into
l1ve709 wants to merge 4 commits into
Conversation
l1ve709
force-pushed
the
fix-daily-challenge-scraper
branch
from
August 19, 2026 22:15
596316b to
3b585cb
Compare
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.
Hey, this PR fixes a few bugs in the newly added Daily Challenge Solver (PR #6) so it can run completely hands-free.
Here is what's fixed:
fetch()requests to their GraphQL API (fetch failed/ 403 errors). I moved the daily challenge fetch logic insidepage.evaluate()so it uses the already authenticated Puppeteer browser. Works perfectly now.python3orgolangbut the user haspythonorgoin their.envfile, which caused the bot to skip the problem. Added a simplelangAliasesmap to normalize these tags before checking.Tested locally with
npm start->[3]and it successfully fetches and submits today's challenge without any manual intervention.