Conversation
|
|
🎉 All green!❄️ No new flaky tests detected 🔗 Commit SHA: b0d3ab8 | Docs | Datadog PR Page | Give us feedback! |
Dev-mode check rejects manifest versions ahead of the current tested tracer (4.9.0-rc1). The cost_tags PR is merged but not yet in any released version. Use missing_feature for now; bump to a concrete version once released. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b2177afdf9
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
sabrenner
left a comment
There was a problem hiding this comment.
looks great, thanks for adding these tests! just a couple actionable things and one note for when (if?) we add Java cost tracking tags too
| return span_event.get("meta", {}).get("metadata", {}).get("_dd", {}).get("cost_tags") | ||
|
|
||
|
|
||
| @features.llm_observability_sdk_enablement |
There was a problem hiding this comment.
small request to make a different feature for this! let me know if you need help with that, i think i made a confluence page on it but i can follow up with you on slack!
| llmobs_request = LlmObsAnnotationContextRequest( | ||
| tags={"team": "ml", "feature": "chatbot"}, | ||
| cost_tags=["team", "feature"], | ||
| children=[LlmObsSpanRequest(kind="llm")], |
There was a problem hiding this comment.
i would say actually maybe having two children here and making sure each one gets the tags to make sure they are getting properly added would be a slightly better test, so like
children=[LlmObsSpanRequest(kind="llm"), LlmObsSpanRequest(kind="llm")],
# ...
assert _get_cost_tags(span_events[0]) == ["team", "feature"]
assert _get_cost_tags(span_events[1]) == ["team", "feature"]just to be extra sure!
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 129254e0e3
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| tests/parametric/test_library_tracestats.py::Test_Library_Tracestats::test_sample_rate_0_TS007: missing_feature (failure 2.8.0) # Created by easy win activation script | ||
| tests/parametric/test_library_tracestats.py::Test_Library_Tracestats::test_successes_errors_recorded_separately_TS006: missing_feature (failure 2.8.0) # Created by easy win activation script | ||
| tests/parametric/test_library_tracestats.py::Test_Library_Tracestats::test_top_level_TS005: missing_feature (failure 2.8.0) # Created by easy win activation script | ||
| tests/parametric/test_llm_observability/test_llm_observability.py::Test_CostTags: missing_feature (cost_tags merged in dd-trace-py#17628, not yet in a released version — bump to the version once released) |
There was a problem hiding this comment.
Quote manifest values containing
#
.cursor/rules/pr-review.mdc requires manifest values with special YAML characters, including #, to be quoted. This new Python manifest declaration includes dd-trace-py#17628 as an unquoted scalar, so it violates the repository manifest YAML syntax rule; wrap the whole value in quotes to keep the manifest compliant and avoid tooling/parsing surprises if the reason text is edited.
Useful? React with 👍 / 👎.
sabrenner
left a comment
There was a problem hiding this comment.
two non-blocking comments, feel free to address! otherwise good to go, just looks like the linter is failing & blocking tests from running
| } | ||
| # cost_tags was added later — only forward when set so older SDK versions | ||
| # without the kwarg don't break unrelated tests in the same weblog. | ||
| if options.get("cost_tags") is None: |
There was a problem hiding this comment.
i think if we gate the tests that run cost tracking behind the version that it's released in, we don't need this line here, but not blocking
Co-authored-by: Sam Brenner <106700075+sabrenner@users.noreply.github.com>
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The prod tracer image runs python@4.8.0 (pre-#17628), which raises TypeError on LLMObs.annotate(cost_tags=...). Restoring the defensive pop so unrelated annotate-using tests (Test_Enablement, Test_Prompts) keep passing on prod. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Motivation
Add system tests for parameter
cost_tags.Changes
Workflow
🚀 Once your PR is reviewed and the CI green, you can merge it!
🛟 #apm-shared-testing 🛟
Reviewer checklist
tests/ormanifests/is modified ? I have the approval from R&P teambuild-XXX-imagelabel is present