You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(explorer): Properly escape transaction names in Snuba queries (#97591)
Fixes
[SEER-2X5](https://sentry.io/organizations/sentry/issues/6803858981/).
The issue was that: Transaction name containing SQL query unescaped into
Snuba search query, causing parse error and 400 Bad Request.
- Encloses the transaction name in double quotes when constructing the
Snuba query string in `index_data.py`. This prevents parsing errors when
the transaction name contains special characters, such as SQL queries.
- Adds a test script `test_transaction_name_escaping.py` to verify that
transaction names with problematic characters are properly escaped.
This fix was generated by Seer in Sentry, triggered by Rohan Agarwal. 👁️
Run ID: 752838
Not quite right? [Click here to continue debugging with
Seer.](https://sentry.io/organizations/sentry/issues/6803858981/?seerDrawer=true)
### 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.
---------
Co-authored-by: seer-by-sentry[bot] <157164994+seer-by-sentry[bot]@users.noreply.github.com>
Co-authored-by: Rohan Agarwal <[email protected]>
0 commit comments