traceloop / traceloop/openllmetry
๐ Bug Report: disabled tests for GCP / VertexAI
Open
Nobody has claimed this yet.
good first issue
help wanted
testing
- Dominant language
- Python
- Stars
- 7.4k
- Forks
- 1.1k
- Avg merge
- 8d 14h
- Merged PRs (30d)
- 2
Description
Which component is this bug for?
VertexAI Instrumentation
๐ Description
Following #413, I had to disable the VertexAI tests since vcr.py doesn't support GRPC. We need to figure out how to mock those requests to avoid making actual calls to GRPC.
๐ Reproduction steps
N/A
๐ Expected behavior
N/A
๐ Actual Behavior with Screenshots
N/A
๐ค Python Version
No response
๐ Provide any additional context for the Bug.
No response
๐ Have you spent some time to check if this bug has been raised before?
- I checked and didn't find similar issue
Are you willing to submit PR?
None
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up โ it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the disabled VertexAI instrumentation tests and reading how they currently use vcr.py. Investigate the test setup for a way to mock gRPC requests without contacting VertexAI; done means the tests run reliably without real gRPC calls and are re-enabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- google-cloud, python
- Domain
- observability, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100