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
{{ message }}
This repository has been archived by the owner on Dec 5, 2019. It is now read-only.
Since Arbiter knows specifically which requirements were unsatisfiable or in conflict, it should ask the user what to do, instead of just blindly erroring out.
This could then be used to "resume" the dependency resolution process, by assuming that the user-given solution is valid.
We should only do this with the actual fatal error, though—this shouldn't happen if a solution may still exist.
The text was updated successfully, but these errors were encountered:
Since Arbiter knows specifically which requirements were unsatisfiable or in conflict, it should ask the user what to do, instead of just blindly erroring out.
This could then be used to "resume" the dependency resolution process, by assuming that the user-given solution is valid.
We should only do this with the actual fatal error, though—this shouldn't happen if a solution may still exist.
The text was updated successfully, but these errors were encountered: