Skip to content

GCE GAPIC is not applying timeout or retry from config file #1905

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.

Sign up for GitHub

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

Jump to bottom
Open
vchudnov-g opened this issue Jan 12, 2024 · 0 comments
Open

GCE GAPIC is not applying timeout or retry from config file #1905

vchudnov-g opened this issue Jan 12, 2024 · 0 comments
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@vchudnov-g
Copy link
Contributor

The compute_grpc_service_config.json defines a timeout and a retryPolicy that are NOT being applied in the generated GAPIC's transports/base.py.

By way of comparison, vision_grpc_service_config.json defines the same timeout and a retryPolicy that ARE being applied in the generated GAPIC's transports/base.py.

This suggests the generator or higher level pipelines are not reading the these policies. It's possibly a REGAPIC- or DIREGAPIC-specific issue.

Tangentially related: #1897
@vchudnov-g vchudnov-g added type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. priority: p2 Moderately-important priority. Fix may not be included in next release. labels Jan 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@vchudnov-g