-
Notifications
You must be signed in to change notification settings - Fork 62
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
conflict with git precommit hook #149
Comments
Is the hook asking for some input? Or is it "just" a matter of the output not being what zest.releaser expects? |
It does not ask for input - so probably "just" a matter of the output not being what zest.releaser expects |
I have that codeanalysis thingy in one of my own projects, too, but I haven't seen a problem with fullrelease. You're saying that you see a lot of output from the hook. I fixed the few errors that codeanalysis reported (and quieted down the rest) for that project of mine before releasing it, so I didn't have the problem. Can you paste the first and last 20 lines of output? Perhaps than we can spot something that throws zest.releaser off guard. @mauritsvanrees: do you have any clue? You're probably using the codeanalysis recipe more often than I do :-) |
My guess is that it could be the amount of output that causes the problem. I had my hook on a bobtemplate project, so a lot of what I consider false negatives (generated bootstrap files etc.). These I can of course ignore. But for now it is good for debugging the problem...
...
|
I was going to say: "I cannot reproduce this." But I can. :-) That has this recipe:
All goes fine then. But then I make a few changes so the script checks the current directory and does not exclude parts/omelette:
Running I wonder if code-analysis has somehow eaten up the output. |
@mauritsvanrees no, first time seeing it... looks weird, I will try to look at it |
Is this still a problem? (I'm looking through old issues) |
UP ! |
Brainstorming: does one of the pre-commit hooks "mess" with the stdin/stdout? @odelaere : do you have more details? Which pre-commit hooks you're using, for instance? |
@reinout Nothing mess in the terminal. it just hangs waiting (I suppose) for something to respond. |
@reinout It appears zest keep hanging while trying to commit if the pre-commit hook returns a failure. |
It doesn't hang for me, it just continues without committing, which is very confusing. |
plone.recipe.codeanalysis installs a precommit hook running flake8 etc. But the output from the hook causes zest.releaser to hang:
and nothing happens (waited several minutes)
Running the git command manually afterwards works fine - but with a lot of output from the hook.
Removing the hook makes the prerelease proces work. (After reverting and restarting)
The hook output in my case is very long (above 600 lines of text). I'm not sure if smaller amounts of hook output causes any trouble.
Traceback from ctrl-c, if it can help:
The text was updated successfully, but these errors were encountered: