feat: truncate oversized event payloads in session response#524
Merged
Conversation
RAG tool results can return KB document content exceeding 1MB per event, causing the frontend TraceSurface to run out of memory when loading large sessions. Truncate tool_result and observation payloads at 1MB in the get_session endpoint, marking truncated events with _truncated: true. The LLM context builder reads from a separate content-only store and is unaffected by this truncation. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Collaborator
|
Thanks for your contribution! |
pancacake
added a commit
that referenced
this pull request
May 27, 2026
Security: lock down the TutorBot tool sandbox (shell exec is opt-in, all filesystem/shell access confined to the bot workspace) and isolate per-user resources, closing #518, #517, #516, #515, #514 and #506 (first hardened in #507). Bug fixes: chat input disabled after the first turn (#520), KB embedding failure on long documents (#521 / #509), profile creation under Docker (#512 / #513), Qwen reasoning models failing native tool calling (#527 / #528), the GPT-5 init-wizard token parameter (#508), and oversized session-event truncation (#524). Features: HTTP/SSE API for multi-turn chat with a specific TutorBot (#511), multimodal image fallback for vision-capable providers without a capability entry, safe ZIP knowledge upload, and a /settings/network page with model fetching (community PRs #522 and #523 reimplemented locally). Also bumps __version__ to 1.4.1, adds the v1.4.1 release notes, updates the README Releases section, and ships the Astro + Starlight docs site under site/. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
anideebee7
added a commit
to intelli-verse-x/DeepTutor
that referenced
this pull request
Jun 6, 2026
The upstream v1.4.2 sync brought tests/api/test_sessions_truncation.py but its
implementation was lost during the original fork merge, leaving the test red
and (because it errored at collection) masking the rest of the smoke suite.
Restore _truncate_oversized_events + MAX_EVENT_PAYLOAD + _TRUNCATION_NOTICE and
wire it into GET /sessions/{id} so oversized tool-result/observation payloads
are trimmed in the history response.
Co-authored-by: Cursor <cursoragent@cursor.com>
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
2 participants
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.
RAG tool results can return KB document content exceeding 1MB per event, causing the frontend TraceSurface to run out of memory when loading large sessions. Truncate tool_result and observation payloads at 1MB in the
get_sessionendpoint, marking truncated events with_truncated: true.The LLM context builder reads from a separate content-only store and is unaffected by this truncation.
Test plan
_truncated: trueis set