Conversation
Bot memory grew steadily because the grammy runner keeps every in-flight update context alive until its handler promise settles (sink timeout defaults to infinity), and several outbound calls could hang forever: generateText with no deadline, embeddings requests with no Effect.timeout, yt-dlp with no spawn timeout, and ky response body reads that ky's headers-only timeout never bounds. Each pinned context also held a full base64 copy of the message attachments, so every hang added permanent megabytes. - Add a 120s total timeout to Llm.invoke; log invocation errors - Add Effect.timeout to embeddings requests (30s image, 10s query) - Kill yt-dlp after 180s; abort direct video downloads so the temp-dir cleanup always runs - Pass AbortSignal.timeout to ky calls that stream response bodies - Load attachment bytes from S3 only on the AI reply path instead of pinning base64 on every group message context - Clamp the client-controlled inline-query offset to 1000 - Add a 10-minute runner sink timeout that evicts stuck updates and logs their id and type, covering hang sites without per-call deadlines (Telegram API calls, S3 reads)
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
1 participant
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.
No description provided.