Tomas Varneckas

I've also encountered this when upgrading from 0.x to 1.1.0. Could it be related to this commit removing this logic of copying resource name into the rack request span? https://github.com/DataDog/dd-trace-rb/commit/f7b664bf196db7197010491aaa96c2174cb773fb#diff-c7c7564cc5bbf99b570001291ddb26f2f03c6804a3727a0a721a8da8658eaeefL45...

I made this monkey patch that ports the old `try_setting_rack_request_resource` into 1.1.0 compatible API. As a workaround this fixes the spans for me: ```ruby # config/initializers/datadog.rb module RackResourceNamePatch def start_processing(payload)...

I have another case. With Rails 6 enum now autogenerates negated scopes for each enum value as well and it becomes dangerous to have enum values starting with `not_`. Consider...

I have tested this in our pretty complex Rails application with Puma running in clustered mode and it led to segfaults. There's risk in making it a default. At the...

I had some time to dig into this, I was able to reproduce with our codebase locally, but could not narrow down it entirely. It crashes right on the `Process.warmup`....

Thanks to your tip I managed to narrow it down and find the gem with the issue. It's [memcached](https://rubygems.org/gems/memcached). This gem is abandoned and we use our own [fork](https://github.com/vinted/memcached/tree/v1.8.4) with...

@byroot I can confirm that with your fork there is no issue. 👍