Anton Ovchinnikov

Feature request: check that the "previous" version exists

2

When preparing a release, validate the new release number by checking if there's a release that might be called "previous". Example: when we're releasing version `1.2.4`, `1.2.3` should _probably_ exist.

Original rv.py from Ivan Frohne: http://web.archive.org/web/20010603210413/http://www.frohne.westhost.com/rv11.zip Will probably fix #3

``` c = OPE('asdfasdfasdfvzxc12312321', in_range=ValueRange(0,12312312), out_range=ValueRange(0,2173912837129837129832)) ``` ...yields `OverflowError: math range error`

Error while parsing Baggage header with percent-encoded whitespace

1

### Description At the moment `baggage.Parse` fails when trying to decode a value with percent-encoded whitespace "%20" (and potentially others?). Related issue in "opentelemetry-python" that has a pending fix: https://github.com/open-telemetry/opentelemetry-python/issues/2934...

At the moment `ContinueFromHeaders` function doesn't handle a case properly when `sentry-trace` is empty, and `baggage` is populated with some Sentry data. In this case, the created span should have...

[OTel] Improve Span attributes for Messaging events

1

Extracted from https://github.com/getsentry/sentry-go/issues/557 and https://github.com/getsentry/team-webplatform-meta/issues/32. Re-evaluate how we set operation/description for messaging spans: https://sentry-sdks.sentry.io/performance/otel-demo-checkoutservice:3a93068eca0d4acb9c7865f68ba5183f According to https://develop.sentry.dev/sdk/performance/span-operations/#messagesqueues, we should set `topic.*` attributes. 

Extracted from https://github.com/getsentry/sentry-go/pull/537. ### Problem Associating errors with transactions is generally implemented (see `otel/event_processor.go`), but there's a caveat: the `EventHint` of the event processor has to contain a valid Context...

Implement EventScrubber for PII scrubbing

1

## Summary Implement an event scrubber and scrub events before sending them to the server when `SendDefaultPII` is set to `false` (which is the default). ## Motivation Various event fields...

## Summary Capture panics in OpenTelemetry-instrumented code and send errors to Sentry. ## Motivation At the moment people have to manually defer `sentry.Recover()` or `sentry.RecoverWithContext()` calls to catch panics. For...