chore(deps): bump ddtrace from 2.19.0 to 2.19.1

[dependabot]

Bumps ddtrace from 2.19.0 to 2.19.1.

Release notes

Sourced from ddtrace's releases.

2.19.1

Bug Fixes

• Profiling

  • Fixes an issue where the memory allocation profiler can cause a segmentation fault due to data races when accessing its own global data structures from multiple threads.
  • Fixes a bug where profiling mutexes were not cleared on fork in the child process. This could cause deadlocks in certain configurations.
  • Removes a system call from the memory allocation profiler, used to detect forks, which ran on every allocation and resulted in a significant slowdown.

• Tracing

  • django: Fixes issue where django cache is represented as a django service rather than the third party service.
  • botocore: Resolves formatting errors in the bedrock integration when parsing request model IDs, which can now accept AWS ARNs.

Changelog

Sourced from ddtrace's changelog.

2.19.1

Bug Fixes

• Profiling

  • Fixes an issue where the memory allocation profiler can cause a segmentation fault due to data races when accessing its own global data structures from multiple threads.
  • Fixes a bug where profiling mutexes were not cleared on fork in the child process. This could cause deadlocks in certain configurations.
  • Removes a system call from the memory allocation profiler, used to detect forks, which ran on every allocation and resulted in a significant slowdown.

• Tracing

  • django: Fixes issue where django cache is represented as a django service rather than the third party service.
  • botocore: Resolves formatting errors in the bedrock integration when parsing request model IDs, which can now accept AWS ARNs.

---

Commits

• c11edb8 fix(profiling): reset all profiling c++ mutexes on fork [backport 2.19] (#11993)
• c9ea15c ci: optimize ci runtime [backport 2.19] (#11937)
• ad2dc85 fix: add schematize service name for django caching [backport 2.19] (#11854)
• e16d68c fix(botocore): accept AWS ARN bedrock model IDs [backport 2.19] (#11971)
• 17a27c9 ci(botocore): fix flaky botocore tests [backport 2.19] (#11969)
• 35b6889 fix(profiling): remove slow getpid call from memalloc path [backport 2.19] (#...
• e24bae1 fix(profiler): update memalloc guard [backport 2.19] (#11878)
• See full diff in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.