-
Notifications
You must be signed in to change notification settings - Fork 1
chore: disable tracing on integration tests #88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -88,6 +88,7 @@ jobs: | |
| image: ghcr.io/astral-sh/uv:python3.12-bookworm | ||
| env: | ||
| UIPATH_JOB_KEY: "3a03d5cb-fa21-4021-894d-a8e2eda0afe0" | ||
| UIPATH_TRACING_ENABLED: false | ||
|
Comment on lines
89
to
+91
|
||
| permissions: | ||
| contents: read | ||
| strategy: | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
UIPATH_TRACING_ENABLEDis set here, but in this repo it appears to be parsed and then never applied (seeUiPathRuntimeContext.with_defaultsinsrc/uipath/runtime/context.py, wheretracing_enabledis computed but not assigned to the context or used to conditionally create/disable a trace manager). Unless another component reads this env var directly, this workflow change likely won’t actually disable tracing for the integration tests. Consider wiring the env var into trace manager initialization (or removing tracing setup when disabled) and/or updating the workflow to use the env var that the tracing implementation actually honors.