feat!: Detect anomalous Datadog traces; upgrade to Python 3.11 #757
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Manual testing:
enable Waffle flag.
self.dd_tracer.current_root_span().finish()
to start ofprocess_view
(faking an anomalous trace) and reinstall in devstackAnomalous Datadog local root span (duration already set): id = 66abf66b000000001168265a391d04a3; duration = 0.108 sec; worker age = 1.560 sec
Unit test improvements:
to 3.11 across our repos, but also because I ran into a really weird bug
with ddtrace and/or jsonschema that only occurs with Python 3.8:
Installing ddtrace breaks tests with the jsonschema library DataDog/dd-trace-py#9950
Merge checklist:
Check off if complete or not applicable: