Skip to content

Revert "Merge pull request #7995 from robx/cleanup-processes" #8295

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

Closed
wants to merge 2 commits into from

Conversation

jneira
Copy link
Member

@jneira jneira commented Jul 17, 2022

This reverts commit ddf3ba2, reversing
changes made to 001e3cc.

pr #7995

I've checked manually a version of branch 3.8 with this reverted and it does not show the problem described here: #8208
This is the fast way to remove the issue for the incoming 3.8 version but ideally the pr should be kept and fixed as the refactor was good.

//cc @robx

@hasufell
Copy link
Member

Why are we reverting? Is there time pressure? The correct way is to fix it.

Please explain exactly what this reversal fixes, on which platform etc. Even after reading #8208 I don't understand it.

@jneira
Copy link
Member Author

jneira commented Jul 17, 2022

The bug and the platform is the title of the linked issue: Interrupting cabal-3.8.0.0.20220526 with ctrl+c makes it hang on windows. Not sure how could be more precise or clearer about that.

The time pressure is mentioned in the last comment of the issue, and also my preference for fixing it.

i would like to examine the pr and find the cause to not having to revert it but i will not have time to not delay the release excessively, what do you think about?

@hasufell
Copy link
Member

-1 for reverting, unless @robx agrees that fixing will take a long time. The way is forward. Releases should be good quality.

@jneira
Copy link
Member Author

jneira commented Jul 17, 2022

-1 for reverting, unless @robx agrees that fixing will take a long time. The way is forward. Releases should be good quality.

Agree, i asked @robx (and include it as reviewer) for that reason. I would not merge this without his approval.
This one would be the last resort to not include the bug in the release. Will mark as draft to make it clearer.

@jneira jneira marked this pull request as draft July 17, 2022 21:50
@Mikolaj
Copy link
Member

Mikolaj commented Jul 18, 2022

For the record, the PR being reverted is #7995. If I understand correctly, this reverts a merge commit, which causes the whole PR to be left out. Let me restart CI to verify if the failure is transient.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants