-
Notifications
You must be signed in to change notification settings - Fork 88
Restore server-side message pagination on HTTP endpoint #21580
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
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
ac3b6fe
feat: add composite DB index and getMessagesPaginated() for message h…
Jasonnnz 854cf86
M2: Wire pagination into handleListMessages HTTP endpoint (#21569)
Jasonnnz 3c86cf7
M3: Client-side safety fixes for pagination edge cases (#21565)
Jasonnnz 53aa620
test: add pagination test suite for handleListMessages (#21578)
Jasonnnz 5cbb375
fix: remove duplicate guard let self in timeout closure (non-optional…
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
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
9 changes: 9 additions & 0 deletions
9
assistant/src/memory/migrations/196-messages-conversation-created-at-index.ts
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,9 @@ | ||
| import type { DrizzleDb } from "../db-connection.js"; | ||
|
|
||
| export function migrateMessagesConversationCreatedAtIndex( | ||
| database: DrizzleDb, | ||
| ): void { | ||
| database.run( | ||
| /*sql*/ `CREATE INDEX IF NOT EXISTS idx_messages_conversation_created_at ON messages(conversation_id, created_at)`, | ||
| ); | ||
| } |
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 pagination query filters only on
created_at < beforeTimestamp, so if multiple messages share the same millisecond as the page boundary, the next page permanently skips the remaining same-timestamp messages. This is a real data-loss-in-pagination case for legacy/imported conversations where duplicate millisecond timestamps exist, and the commit already exposesoldestMessageIdbut never uses it to disambiguate cursors. Please paginate with a stable(created_at, id)cursor (and request-sidebeforeMessageId) to avoid dropped history rows.Useful? React with 👍 / 👎.