dwave-cloud-client
dwave-cloud-client copied to clipboard
A minimal implementation of the REST interface used to communicate with D-Wave Solver API (SAPI) servers.
Since serialized BQM et al. data is not compressed in dimod anymore, look into benefits of compressing in transit.
In Python >= 3.9, it should be rewritten as follows. ``` python hashlib.md5(usedforsecurity=False) ``` https://github.com/dwavesystems/dwave-cloud-client/blob/442211d5279e9e6a96dc42175549caef66844970/dwave/cloud/client/base.py#L1832-L1834 Please refer to those page. http://blog.serindu.com/2019/11/12/django-in-fips-mode/ https://code.djangoproject.com/ticket/28401
**Description** `DWaveSampler().sample(bqm, num_reads=np.int8(123))` gives an error. Why `np.int8(123)`? Occurs in scenarios such as `np.linspace(2, 6, 10, dtype=np.int8)[0]` **To Reproduce** this will fail with the following error: `TypeError: Object of type...
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...
Currently we cache regions for 24h, which is a safe default. However, if Metadata API response includes `Cache-Control` header, with `max-age` directive, we want to cache for up to `max-age`.
Currently we only use `metadata_api_endpoint` and `headers` because we need to resolve regions mid `Client` construction, i.e. config parsing. Blocked by #504.
Recently refactored `dwave.cloud.config.load_config()` is in a good shape, but we want to completely decouple config parsing from `Client` construction, so that config can be loaded independently and used outside of...
For reproducible runs of user code (e.g. 3rd party library tests), we need a way to turn caching off. An alternative is a MockClient, see #22.
Something like: ``` $ dwave config -f /path/to/file -p profile-name set solver DW_2000Q_6 $ MY_TOKEN=$(dwave config get token) $ dwave config -p test list test.solver = ... test.endpoint = ......