You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This currently can happen if a variable source returns an error when getting variables.
Notably, solve does NOT return an error for UNSAT. This error means "was not able to get variables or setup the solver"
Look for the matching variable in the solution
We skip the step of checking if the solution was SAT or UNSAT. UNSAT currently manifests as an error looking up the bundle entity from the solution. This "works", but it means users don't see the UNSAT reason that comes from solution.Error()
We should check solution.Error(), and handle it accordingly.
The text was updated successfully, but these errors were encountered:
This problem is pretty much solved by operator-framework/deppy#140, which is not yet in a release. We should ask deppy maintainers to create a release with this fix and then our op-con update will be pretty straightforward.
Related to operator-framework/deppy#139 and possibly #329
In
Reconcile
we:Solve
returned an error.We skip the step of checking if the solution was SAT or UNSAT. UNSAT currently manifests as an error looking up the bundle entity from the solution. This "works", but it means users don't see the UNSAT reason that comes from
solution.Error()
We should check
solution.Error()
, and handle it accordingly.The text was updated successfully, but these errors were encountered: