resolver: handle unbounded version requirements in conflict message - #343
Open
micprog wants to merge 1 commit into
Open
resolver: handle unbounded version requirements in conflict message#343micprog wants to merge 1 commit into
micprog wants to merge 1 commit into
Conversation
Half-bounded or wildcard requirements (e.g. `>=1.0`, `*`) have no top and/or bottom bound, which panicked the unwraps when formatting the conflict-resolution message. Render the available bounds instead, and sort unbounded requirements as the extreme version in the sort helpers. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
micprog
force-pushed
the
unbounded_req_panic
branch
from
August 5, 2026 13:49
630bda4 to
62aa463
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Half-bounded or wildcard requirements (e.g.
>=1.0,*) have no top and/or bottom bound, which panicked the unwraps when formatting the conflict-resolution message. Render the available bounds instead, and sort unbounded requirements as the extreme version in the sort helpers.