Repository navigation
fix(trading): page order history by a real keyset cursor, not the same "0:" forever #234
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+381
−108
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The parser accepts any cursor containing a valid ISO timestamp and a nonempty ID, even if the route never issued it. For example,
2026-09-11T10:00:00|unknownis used directly as the database boundary, so the response can silently omit newer orders instead of returning the promised 400. Validate that the cursor identifies an existing order in the applicable result set, or use an opaque authenticated cursor.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed in 4dab50a by narrowing the documented contract, not by validating existence. A cursor is a keyset position, not a token: a well-formed
<created_at ISO>|<order id>pages back from that point whether or not the order exists, the same way the repository'sbeforebound works. Only a malformed cursor gets a 400. Looking the order up would cost a query per page and add nothing for a client that followsnext_cursor. The route and_parse_order_cursordocstrings now say this, andtest_a_well_formed_cursor_is_a_position_even_for_an_order_that_does_not_existpins it.