Skip to content

refactor(o11y): remove google-cloud-unstable-tracing guards and regenerate#5292

Draft
haphungw wants to merge 5 commits intogoogleapis:mainfrom
haphungw:remove-google-cloud-unstable-tracing-guards
Draft

refactor(o11y): remove google-cloud-unstable-tracing guards and regenerate#5292
haphungw wants to merge 5 commits intogoogleapis:mainfrom
haphungw:remove-google-cloud-unstable-tracing-guards

Conversation

@haphungw
Copy link
Copy Markdown
Contributor

@haphungw haphungw commented Apr 5, 2026

No description provided.

@codecov
Copy link
Copy Markdown

codecov bot commented Apr 5, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.78%. Comparing base (e373f94) to head (2ad970b).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #5292      +/-   ##
==========================================
- Coverage   97.79%   97.78%   -0.01%     
==========================================
  Files         220      220              
  Lines       45845    45829      -16     
==========================================
- Hits        44832    44815      -17     
- Misses       1013     1014       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@haphungw haphungw force-pushed the remove-google-cloud-unstable-tracing-guards branch from c86588b to aaabb6e Compare April 5, 2026 13:12
@haphungw haphungw force-pushed the remove-google-cloud-unstable-tracing-guards branch from a1c2fd5 to 60b498d Compare April 6, 2026 12:43
@haphungw haphungw changed the title refactor(o11y): remove google-cloud-unstable-tracing guards and regenerate refactor(o11y): remove google-cloud-unstable-tracing guards and regenerate Apr 6, 2026
@haphungw haphungw force-pushed the remove-google-cloud-unstable-tracing-guards branch 4 times, most recently from 134dd05 to 98362b5 Compare April 7, 2026 07:13
haphungw added a commit that referenced this pull request Apr 7, 2026
Restore the test to use `#[tokio::test(flavor = "multi_thread",
worker_threads = 2)]` so the background server can run on a separate
thread.

I made a mistake when applying `#[tokio::test(flavor = "current_thread",
start_paused = true)]` to `grpc_client_request_success`. This failed
because:
1.  This test does not contain any sleeps to optimize.
2. It starts a background gRPC server, which deadlocks on a single
thread when the client waits for a response.

This surfaces in #5292 when the `unstable_tracing` guards are removed.
@haphungw haphungw force-pushed the remove-google-cloud-unstable-tracing-guards branch 3 times, most recently from 706eb09 to 8accedb Compare April 7, 2026 20:57
haphungw added a commit that referenced this pull request Apr 7, 2026
Add missing feature guards within `gax-internal` for isolation between
HTTP and gRPC transport layers.

Essentially fix build error for #5292.
haphungw added a commit that referenced this pull request Apr 7, 2026
Fix a `gcb-pr-minimal-versions` build failure in
`google-cloud-gax-internal` tests caused by `h2` version `0.4.2`, which
surfaces after `google_cloud_unstable_tracing` guards are removed in
#5292.

The Problem
During minimal-versions checks, `h2` resolves to `0.4.2`, which somehow
leads to deadlocks or missing tracing spans in our gRPC tests.

Previous Attempts
I tried switching tests to `multi_thread` (PR #5308), which masked the
issue but was not a good solution.
I tried forcing the version in the root `[workspace.dependencies]`, but
`Cargo` ignored it during the isolated package build for `gax-internal`.

The Fix
Add `h2 = "0.4.13"` as a direct dependency in
`src/gax-internal/Cargo.toml`. `0.4.13` is the version resolved in our
normal Cargo.lock.
@haphungw haphungw force-pushed the remove-google-cloud-unstable-tracing-guards branch from 8accedb to 2ad970b Compare April 7, 2026 23:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant