fix: Limit the number of timelines fetched #1931
Merged
Conversation
This file contains 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
shakkernerd
changed the title
shakkernerd
approved these changes
Jan 7, 2025
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.
Related Issue
elizaOS/agent-twitter-client#43
Problem
The count parameter is currently not functioning. Based on testing, it appears to be ignored on the server side. This is problematic, as the default behavior fetches a large number of timelines:
fetchHomeTimeline: ~30–40 timelines per request
fetchFollowingTimeline: ~100 timelines per request
For users with the action processing feature enabled, this results in excessive LLM API calls (Reference: #1824 introduced a new environment variable to enable user interactions with following timelines.). In this PR, I used a workaround by slicing the timelines before processing to reduce the number of processed items.