Clarify OpenReview anonymous-access error (anti-bot challenge) - #24
Merged
Conversation
Anonymous OpenReview note queries are now gated behind an anti-bot challenge (HTTP 403 ChallengeRequiredError) for all venues, not just recent ones. Reword the runtime error, .env.example, and README so they say credentials are required (OPENREVIEW_TOKEN or OPENREVIEW_USERNAME + OPENREVIEW_PASSWORD) and drop the inaccurate "some networks / older venues work anonymously" framing.
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
2 participants
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.
Context
Fixes the confusion in #17: an ICLR/NeurIPS run fails with
HTTP 403 Forbidden. The 403 body is an OpenReviewChallengeRequiredError— OpenReview now gates anonymous note queries behind an anti-bot challenge, verified against ICLR 2024 and 2023, both thecontent.venueidandinvitationquery forms, and both theapi2andapihosts. There is no anonymous workaround; credentials are required. (The failure is unrelated to the theme.)The code already supports auth and fails fast with a helpful message — this PR just makes the wording accurate: it was previously framed as "recent venues / from some networks / older venues work anonymously," which no longer holds.
Changes (message + docs only)
conflens/sources.py— reworded theRuntimeErrorto name the anti-bot challenge and the exact env vars (OPENREVIEW_TOKEN, orOPENREVIEW_USERNAME+OPENREVIEW_PASSWORD)..env.example— "Optional … recent venues … some networks" → "Usually required … all anonymous note queries are challenge-gated."README.md— same clarification; dropped "Older venues work anonymously."Testing
ruffclean ·pytest67 passedNo behaviour change — the adapter already authenticates when credentials are present and already raised on the 403; only the human-facing text changed.