Client subclasses not overriding client type from user config
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
Research direction
Start with dwave.cloud.qpu.Client.from_config() and reproduce the DWAVE_API_CLIENT=sw example from the issue. Trace how the configured client type is selected and verify that calling the qpu.Client subclass does not unexpectedly return the configured sw client; done means the subclass and user configuration have the intended precedence.
Written by the indexing model from the issue text.
Description
For example:
$ DWAVE_API_CLIENT=sw python
...
>>> dwave.cloud.qpu.Client.from_config()
<dwave.cloud.client.sw.Client object at 0x7f2864eca2b0>
- Dominant language
- Python
- Stars
- 63
- Forks
- 44
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 2
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from dwavesystems/dwave-cloud-client
-
Add return typehints to sample_ functionsPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
feature
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
dwavesystems/dwave-cloud-client#748 · 1 reaction ·
-
feature
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
dwavesystems/dwave-cloud-client#738 · 1 comment ·
All issues in dwavesystems/dwave-cloud-client
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
google-ai-edge/litert-torch#1346 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
geneontology/gocam-py#272 ·
-
pushed_authorization_request sends list authorization_details as a Python reprPossibly taken @RaphaelFakhri claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
auth0/auth0-python#903 ·
Maintainers usually reply within 1 day