Repository navigation
Fetch the content version before a nonzero read_paper offset - #36
Merged
Merged
Conversation
The Papers API rejects a nonzero chunk offset without the content version, so an offset read now learns the current version from a one-byte read at zero and then continues from the requested byte. The test stub enforces that rule. Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
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.
Summary
content_version. Let read_paper start at a byte offset the caller already holds #35 sent none, soread_paper(offset=N)failed on staging withQuery parameter content_version is required for a nonzero offset.Verification
uv run --offline pytest -q testsinmcp_server: 86 passed.read_paper(2610.23279, offset=81920)returned the error above. This PR fixes it; re-verify after redeploy.🤖 Generated with Claude Code