Repository navigation
fix(cli): stop Sentry from recording frame local variables - #1579
Merged
wcchang1115 merged 1 commit intoOct 21, 2026
Merged
wcchang1115 merged 1 commit into
wcchang1115 merged 1 commit into
Conversation
When a run fails, Sentry records the local variables of each frame, and these include the full dbt manifests. On a large project, one event can reach several GB and keep server memory high for minutes. Turn off include_local_variables, so Sentry events no longer carry frame locals. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Wei-Chun, Chang <wcchang@infuseai.io>
wcchang1115
marked this pull request as ready for review
October 21, 2026 08:58
wcchang1115
deleted the
feature/drc-4940-recce-server-memory-grows-from-1-gb-to-5-7-gb-when-a-run
branch
October 21, 2026 08:59
Codecov Report✅ All modified and coverable lines are covered by tests.
... and 3 files with indirect coverage changes 🚀 New features to boost your workflow:
|
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
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.
PR checklist
What type of PR is this?
fix
What this PR does / why we need it:
When a run fails,
recce/apis/run_func.pysends the exception to Sentry. By default, Sentry records the local variables of each frame in the traceback and callsrepr()on them. These locals can include aDbtAdapter. It is a dataclass, so itsrepr()includes the fullmanifestandbase_manifest. On a large dbt project, one Sentry event can reach several GB, and the server keeps that memory until the upload ends.This PR passes
include_local_variables=Falsetosentry_sdk.init.Which issue(s) this PR fixes:
Special notes for your reviewer:
Sentry events no longer carry frame local variables for any error, not only for failed runs.
Does this PR introduce a user-facing change?:
🤖 Generated with Claude Code