generated from amazon-archives/__template_Apache-2.0
-
Notifications
You must be signed in to change notification settings - Fork 104
fix(memory): paginate list_messages by converted message count, not raw event count #347
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
Open
Hweinstock
wants to merge
1
commit into
aws:main
Choose a base branch
from
Hweinstock:fix/list-messages-pagination
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,42 @@ | ||
| """Reusable pagination utility for fetching and converting paginated results.""" | ||
|
|
||
| from typing import Any, Callable, TypeVar | ||
|
|
||
| T = TypeVar("T") | ||
| R = TypeVar("R") | ||
|
|
||
| DEFAULT_PAGE_SIZE = 100 | ||
|
|
||
|
|
||
| def paginate_for_n_results( | ||
| fetch_page: Callable[[dict[str, Any]], tuple[list[R], str | None]], | ||
| initial_params: dict[str, Any], | ||
| converter: Callable[[list[R]], list[T]], | ||
| target_count: int, | ||
| ) -> list[T]: | ||
| """Paginate an arbitrary API, converting accumulated results after each page. | ||
|
|
||
| The full accumulated list is re-converted after each page rather than converting | ||
| per-page, because some converters (e.g. events_to_messages) iterate the input in | ||
| reverse — converting per-page would produce incorrect ordering. | ||
|
|
||
| Args: | ||
| fetch_page: Takes params dict, returns (items, next_token). next_token is None when exhausted. | ||
| initial_params: Base params for the first call. "nextToken" is added for subsequent pages. | ||
| converter: Converts accumulated raw items to desired output type. | ||
| target_count: Stop after collecting this many converted items. | ||
| """ | ||
| all_items: list[R] = [] | ||
| next_token: str | None = None | ||
|
|
||
| while True: | ||
| params = {**initial_params} | ||
| if next_token is not None: | ||
| params["nextToken"] = next_token | ||
|
|
||
| items, next_token = fetch_page(params) | ||
| all_items.extend(items) | ||
|
|
||
| converted = converter(all_items) | ||
| if len(converted) >= target_count or next_token is None: | ||
| return converted[:target_count] |
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
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.
This bypasses
MemoryClient.list_eventsand callsgmdp_client.list_eventsdirectly.MemoryClient.list_eventswraps the raw API with error handling (catchesClientError), parameter normalization, and filter construction — none of that applies here. It also means the session manager now has two different data-plane access patterns: every other method goes throughMemoryClient, butlist_messagesreaches through to the internal client. If someone later adds logging or error normalization toMemoryClient.list_events, this code path silently misses it.Recommendation: Add a paginated variant to
MemoryClient— e.g.,list_events_page(memory_id, actor_id, session_id, max_results, next_token) -> (events, next_token)— that wraps the raw API call with the same error handling. Thenfetch_pagecalls that instead of reaching through togmdp_client.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 challenge here is that the
list_eventswrapper in MemoryClient already paginates, but does so in a way that is incompatible with this fix (still counts agent state towards max results).I thought about trying to generalize the existing MemoryClient method, but doing so in a backwards-compatible way is going to be difficult.
For those reasons, I chose to drop down to the raw client to control the pagination myself.