googleapis / googleapis/google-cloud-rust
BigQuery `JobPoller` integration tests stack overflow when tracing is enabled
- Dominant language
- Rust
- Stars
- 955
- Forks
- 144
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 279
Description
The problem might be the size of the generated BigQuery structs (`InsertJobRequest` and `JobConfiguration`). When tracing is enabled, the observability middleware captures these large payloads across `.await`. This causes the compiler to generate a large future, which exhausts the thread stack capacity.
https://github.com/googleapis/google-cloud-rust/pull/6232#discussion_r3785127654
Contributor guide
Research direction
Start with the discussion in pull request #6232 and reproduce the BigQuery JobPoller integration test failure with tracing enabled. Inspect how InsertJobRequest and JobConfiguration are captured across .await; done means the integration tests no longer overflow the thread stack when tracing is enabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- google-cloud, rust
- Domain
- observability, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100