Respect low-level solver order on failover #480
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
randomir
force-pushed
the
bugfix/respect-low-level-solver-order-on-failover/issue-479
branch
from
66147b7 to
e0a6921
Compare
randomir
force-pushed
the
bugfix/respect-low-level-solver-order-on-failover/issue-479
branch
2 times, most recently
from
1b0a61f to
e0a6921
Compare
arcondello
approved these changes
Nov 7, 2022
randomir
deleted the
bugfix/respect-low-level-solver-order-on-failover/issue-479
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix #479.
The amount of
dwave.cloud.Client.get_solvercode/functionality replication turns out to be less then expected. Still not ideal, but probably the best solution without/until cloud-client config refactor.