-
Notifications
You must be signed in to change notification settings - Fork 703
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
Revert "add marked output to cabal list-bin
"
#8668
Conversation
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.
LGTM. Please kindly emergency-merge after getting 2 reviews, without the waiting period.
Edit: if needed.
@Cmdv: I tried to add you to the reviewers field, but I can't because you don't have the proper repo permission. I've sent an invite with these. |
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.
LGTM 🚢
@Mikolaj In the original PR there was mention this area lacking tests. Any recommendations as to what/where these should look like? |
I think @andreasabel has some ideas (and questions) in other tickets. |
cool I'll have a look I spotted you mentioned there were "some" tests but they were false positives/not catching this case :) |
Yes. We collectively messed up. :) |
haha we can all point fingers at each other then no one is to blame!! :) |
it wasn't me!!! |
If I'm not mistaken, this one is not needed any more thanks to merging #8670. @andreasabel: amazing search&rescue just in time for 3.10. Closing. |
Reverts
cabal list-bin
#8622Said PR didn't solve #8400 properly and introduced regression #8664. As 3.10 cut is imminent, I propose a swift action here, giving us peace to solve #8400 without time pressure.
Fixes #8664.
Update: I have prepared another PR, #8670, that fixes #8400. If we manage to merge that one quickly, we do not need the present PR.
cabal list-bin
#8670