-
Notifications
You must be signed in to change notification settings - Fork 697
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
Add a format rejections function #9560
Conversation
@yvan-sraka I would like to get this in before some formatting changes for showing "constraint from project". This is a subset of your #9541 changes. |
73540ec
to
a5f2cc8
Compare
@Mikolaj I had to rerun failed jobs three times to get all green ticks: Failures were:
|
@philderbeast thanks for the report. The work to prevent this bug is under way in #9540 If you have energy, your help there would be greatly appreciated because I'm running out of ideas. |
a5f2cc8
to
c0c36ec
Compare
Label |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we get @grayjay's opinion on it but any chance? She's our solver code owner effectively. Would be great to get her approval on any change to it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@philderbeast Thanks for working on the solver error messages! Please add a note about starting with @yvan-sraka's change to the commit message.
cabal-install-solver/src/Distribution/Solver/Modular/Message.hs
Outdated
Show resolved
Hide resolved
cabal-install-solver/src/Distribution/Solver/Modular/Message.hs
Outdated
Show resolved
Hide resolved
c0c36ec
to
472d2f1
Compare
@yvan-sraka I did not start from your change and sorry I didn't see your work on #4251 earlier. I was working on #9510 and the verbosity of the rejection messages started to annoy me so I raised #9559, saw a quick fix improvement and went for it, found your work and realized I hadn't accounted for hyphenated package names. The commit history is lost after squashing but these were the 3 initial commit messages:
|
@philderbeast Sorry, I had misunderstood your comment above. I see that the changes are independent. |
70f8a76
to
a79cf19
Compare
I've left recent commits as-is for review. Please let me know if you'd like some of these squashed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@philderbeast Thanks for the updates and for also handling skipped versions.
I've left recent commits as-is for review. Please let me know if you'd like some of these squashed.
I would prefer squashing to remove the large test build files before you merge.
cabal-install-solver/src/Distribution/Solver/Modular/Message.hs
Outdated
Show resolved
Hide resolved
cabal-install-solver/src/Distribution/Solver/Modular/Message.hs
Outdated
Show resolved
Hide resolved
cabal-install-solver/src/Distribution/Solver/Modular/Message.hs
Outdated
Show resolved
Hide resolved
cabal-install-solver/src/Distribution/Solver/Modular/Message.hs
Outdated
Show resolved
Hide resolved
cabal-install-solver/src/Distribution/Solver/Modular/Message.hs
Outdated
Show resolved
Hide resolved
cabal-install-solver/src/Distribution/Solver/Modular/Message.hs
Outdated
Show resolved
Hide resolved
5eefeee
to
cf9161f
Compare
- Is for instances, Vs for versions
Leave commentary that goPReject and goPSkip reverse the order of instances
7bb55b7
to
5bceb40
Compare
cabal-install/tests/UnitTests/Distribution/Solver/Modular/Solver.hs
Outdated
Show resolved
Hide resolved
@ulysses4ever this is ready for your approval. It already has the merge delay passed label attached. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perfect, thanks!
Label merge+no rebase is necessary when the pull request is from an organisation. |
Please, try not to forget squashing before merging. |
@ulysses4ever a momentary lapse of diligence on my part, sorry about that. |
Fixes #9559. Helps with #4251.
Template Α: This PR modifies
cabal
behaviourInclude the following checklist in your PR:
The documentation has been updated, if necessary.To test, introduce a version bound (or conflict) that is going to reject some versions of a package. Even if this creates an unsolvable combination of versions, that should suffice to trigger the rejection message by the solver for manual testing.
I found no examples of solver rejection messages in the docs.