Alex Robbin
Alex Robbin
Whoops, I screwed up when simplifying the test case, I've updated the relevant code!
That's great @presidentbeef! I'm afraid I might be in over my head with trying to write a PR for this, but if you have any tips, I can give it...
For those who are still looking for a potential solution to this problem, and are also using Rails and RSpec, I took this approach: ```ruby module FactoryBotFileFixtureHelpers extend ActiveSupport::Concern include...
@marcotc yep! We went from 0.54.1 to 0.54.2, which also included the following gem updates: * debase-ruby_core_source 0.10.12 -> 0.10.14 * msgpack 1.4.2 -> 1.4.3
Happy to share some more details! We do not have profiling enabled (we trialed it at some point in the past, months ago, but it is not currently enabled). Here...
I was able to try this in our staging environment, and it does seem to be happening on v0.54.1 as well. It's definitely weird that we didn't see this output...
@ivoanjo done!
@akapronik @ivoanjo unfortunately I don't have any news here. I raised the issue with Datadog Support, and the last update I received was that Engineering is looking into the issue....
Similar to what @llxff said, we're seeing this and I believe it's due to our enabling of the `:request_queuing` configuration option in the Rack instrumentation. That becomes the top-level span...
@delner am I right in thinking that the change you alluded to in v1.3.0 wrt the `rack.request` span name is #2180? If so, that makes a lot of sense, and...