Skip to content
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

Client init fails in 0.9.2 if proxy/permissive_ssl is required #507

Closed
randomir opened this issue Nov 26, 2021 · 1 comment · Fixed by #568
Closed

Client init fails in 0.9.2 if proxy/permissive_ssl is required #507

randomir opened this issue Nov 26, 2021 · 1 comment · Fixed by #568
Labels
bug

Comments

@randomir
Copy link
Member

We currently resolve region (using Metadata API) during Client construction. If proxy or permissive_ssl options are required for Metadata API requests (in addition to SAPI requests), region resolution (and Client init) will fail as those options are not parsed in time.

Implementing #505 will fully resolve this, but we might want to address it with a partial fix sooner.
@randomir randomir added the bug label Nov 26, 2021
@randomir
Copy link
Member Author

randomir commented Jan 3, 2023

Temporary workaround is to explicitly specify endpoint, in which case endpoint/region is not resolved (and request to Metadata API is never made).

@randomir randomir mentioned this issue Jan 3, 2023
Closed
@randomir randomir mentioned this issue Sep 6, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Consolidate config parsing and validation randomir/dwave-cloud-client
1 participant
@randomir