Keep the GraphQl end cursor to avoid getting the data twice#2406
Merged
Conversation
Urgau
changed the title
Kobzol
approved these changes
May 16, 2026
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.
For some reason GitHub GraphQl api doesn't seems to send anymore a response object at all when we pass the last cursor.
This trigger a bug where we though we had new data (actually the old one) and so everything was duplicated.
This PR fixes it by making sure we never lose a cursor, even if the GraphQl doesn't send one anymore.
Testing: http://localhost:8000/gh-comments/rust-lang/rust-forge/pull/1040