James Crosswell

> Wdyt @bitsandfoxes @jamescrosswell ? From memory, we initially pushed this back to 5.0.0 from 4.0.0 to descope the 4.0 release a bit and make sure we'd be able to...

I'm pretty sure all of the above will be addressed in [Fix/DB Connection spans presented poorly #2409](https://github.com/getsentry/sentry-dotnet/pull/2409). The `Trying to close a span that was already garbage collected` error was...

Closing this issues as it should be fixed with the [3.33.1](https://github.com/getsentry/sentry-dotnet/blob/3.33.1/CHANGELOG.md#3331) release.

We now have separate issues for each of the items mentioned here and we already have the feat/4.0.0 pull request as an umbrella to sit across these (plus all the...

Since we [decided not to implement #190](https://github.com/getsentry/sentry-dotnet/issues/190#issuecomment-1491065903), maybe this also needs to be closed?

From what I can tell, this was implemented about 3 years ago in https://github.com/getsentry/sentry-dotnet/pull/1296 so there's nothing to do here: https://github.com/getsentry/sentry-dotnet/blob/175623c91c7c7a660ed3a5bafb6d4bd31ba86cb7/src/Sentry/TransactionTracer.cs#L373-L380

> For the historical github flow (before squash and rebase merges were available on github), it would be _more_ surprising (IMO) to have the HEAD run CI, since that doesn't...

@sunshowers I'd be really interested to hear specific examples of how/where `ref: ${{ github.event.pull_request.head.sha }}` could get us in trouble... if you've got any.

> There is an open issue about supporing this in runtime repo, will find it and link from here. @cijothomas I'd be interested in that issue, if you're still able...

Thanks @cijothomas. Do you think there's any possibility of working around this in the OpenTelemetry API until that issue in the dotnet runtime gets resolved? That issue has been open...