fix(query_builder): Remove noisy "Tag value was not a string" diagnostic - #122946
Draft
sentry[bot] wants to merge 1 commit into
Draft
fix(query_builder): Remove noisy "Tag value was not a string" diagnostic#122946sentry[bot] wants to merge 1 commit into
sentry[bot] wants to merge 1 commit into
Conversation
Contributor
Backend Test FailuresFailures on
|
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.
This PR removes a diagnostic
sentry_sdk.capture_messagethat was generating excessive noise for issue SENTRY-VD5, 'Tag value was not a string'.The issue occurred in
src/sentry/search/events/builder/base.pywhen processing tag values that were not strings, specifically whenis:unresolvedin dashboard queries was parsed tostatus=0(an integer). The code correctly handled this by coercing the value to a string (value = str(value)), but a diagnosticcapture_messagewas left in place, logging an error for a perfectly valid and handled scenario.This change removes the
sentry_sdk.set_tag,sentry_sdk.set_attribute, andsentry_sdk.capture_messagecalls, eliminating the unnecessary error reports without affecting the query builder's functionality.Legal Boilerplate
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.
Fixes SENTRY-VD5
Fixes DAIN-1805
Comment
@sentry <feedback>on this PR to have Autofix iterate on the changes.This PR was automatically generated by Sentry. You can adjust this setting at any time.