Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve solve failure explanations by using better wording #6366

Merged
merged 1 commit into from
Feb 14, 2023

Conversation

jhawthorn
Copy link
Contributor

* Replaces the wording of "is forbidden" with "cannot be used"
* Fixes the method signature of VersionRange::Empty#eql?

Co-authored-by: Daniel Colson <danieljamescolson@gmail.com>
@deivid-rodriguez deivid-rodriguez changed the title Update pubgrub Improve solve failure explanations by using better wording Feb 13, 2023
@deivid-rodriguez
Copy link
Member

Let's see how merge queue behaves on potentially conflicting PRs.

Copy link
Member

@deivid-rodriguez deivid-rodriguez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this @jhawthorn!

@deivid-rodriguez deivid-rodriguez added this pull request to the merge queue Feb 13, 2023
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to no response for status checks Feb 13, 2023
@deivid-rodriguez deivid-rodriguez added this pull request to the merge queue Feb 13, 2023
Merged via the queue into rubygems:master with commit 855991c Feb 14, 2023
deivid-rodriguez added a commit that referenced this pull request Feb 15, 2023
Improve solve failure explanations by using better wording

(cherry picked from commit 855991c)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ArgumentError: wrong number of arguments (given 1, expected 0)
3 participants