Romain Komorn

My only commit for this release is https://github.com/DataDog/dd-trace-py/commit/3363812e6778bba1df6f94bcb43cb002afe6a8b5 so think I'm going to, respectfully, bow out. That said, this looks very similar to https://github.com/actions/runner-images/issues/4733 . I don't know if our...

I work on the `pytest` plugin, so I figured I'd take a look at this (and #4179, at least temporarily), although it looks like the reports here are explicitly not...

@matroscoe , since you're not using (or you're disabling) the `ddtrace` plugin for `pytest`, I assume you're installing `ddtrace` as a dependency for the purpose of using it in the...

@jlucas91 , I think there are two (maybe three) separate issues here: First, I did notice today that it looks like we have a problem with Python 3.10+ that I...

I don't think it's related to recent changes (we haven't touch our usage of `rootdir`). @braingram , from reading this issue, I'm not getting the sense that this is a...

I just did a quick "bisect" (with `pip`, not `git`) and it looks like this is an issue introduced in `2.x`. Tracking this with CIVIS-9265 .

https://github.com/DataDog/dd-trace-py/pull/7627 is what introduced the incompatibility with `-p no:legacypath` , although I'm assuming using ITR would also cause an error because of the places we access `config.rootdir` (like https://github.com/DataDog/dd-trace-py/blob/1.20/ddtrace/contrib/pytest/plugin.py#L83 and...

Hi @hdadkhah1 , thanks for the crash report. We did merge #8328 into this release, but that only addresses the cases where the exception happens in our code, and it...

Given the recent changes made for this and https://github.com/DataDog/dd-trace-py/issues/8281#issuecomment-2096705267 , I'm going to mark this as closed as well. Since there have been multiple different (but related) issues (gevent deadlocks,...

#9586 should address this.