Ivo Anjo

Given that we ended up not using it, shall we go ahead and close this PR for now?

I'm going to go ahead and close this one, since we ended up not using it for now :)

Thanks a lot @tjk for the report. This definitely looks similar to the mysql2 issue another customer reported [(see known issues in the release notes)](https://github.com/DataDog/dd-trace-rb/releases/tag/v1.10.0). You mentioned that > EDIT:...

I was able to reproduce this easily -- thanks for the clear notes! It's indeed the same issue as [called out in the release notes for the mysql2 gem](https://github.com/DataDog/dd-trace-rb/releases/tag/v1.10.0). I...

Update: I've reported the issue to the [libssh2 developers](https://github.com/libssh2/libssh2/issues/955) and also asked the [rugged developers](https://github.com/libgit2/rugged/issues/959) if they'd be open to shipping a workaround built-into the gem.

Looks like there's a PR to fix libssh2 ( https://github.com/libssh2/libssh2/pull/1058 ), hopefully it will get accepted soon.

Thanks for the patience! I've replied to all the notes + applied a few suggested changes. I've also gotten a :+1: from @nsavoire on the weird C bits, so if...

It's been almost a year since I've opened this. This was an R&D week thing, and I ended up not getting back to it, and then kinda fell in the...

Hey @dostaglou I spoke with a few colleagues and they suggested trying to set the `track_error` tag to `true`. Let us know if that works for you :)

It should go on the same span as you're calling `set_error`.