First invalid tag key causes weird tag on issue details

[leeandher]

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

1. Set two invalid tag key in the SDK:

sentry_sdk.set_tag('slash/1', 'some-value')
sentry_sdk.set_tag('slash/2', 'some-value-2')

2. Cause an error
3. Go to issue details for the page

Expected Result

Since those tags were invalid, I'd expect the keys and values to be dropped. They should both appear at the top of the page as invalid, and I wouldn't expect to see some-value or some-value-2 anywhere.

Actual Result

We only show an actionable call out for one of the dropped tags, even though both were omitted, and for some reason we retain the first error's value, causing us to display null: some-value.

I thought the bug could be in serialization, but in event.py, get_tags_with_meta fn, it appears to already save the event with a raw tag of [None, 'some-value'] meaning the bug takes place before that. I don't know why the second dropped tag is being omitted.

Product Area

Issues

Link

https://sentry-leander.sentry.io/issues/5312471138/?project=5900755&query=is%3Aunresolved&referrer=issue-stream&statsPeriod=30d&stream_index=0

DSN

No response

Version

No response