-
-
Notifications
You must be signed in to change notification settings - Fork 59
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
CalledProcessError attempting to add a blurb #275
Comments
Running the command manually succeeded. Not sure why git would fail with an exit code of 128 and not emit any output. Oh, because the code swallows the output. |
Running a second time with pdb, I did not encounter the error (though I did encounter another error):
|
@jaraco how is git put on your PATH? It looks like |
I'm on macOS 10.13.6 with I honestly can't imagine what might have gone wrong. I tried running the command a couple more times (same as before), but this time didn't encounter the error. Still, I wonder if it would be better to let the output from the git invocation be piped directly to stdout/stderr:
Or if there's some reason to capture the output (there isn't any output at all in my use case), use that output when reporting an exception. |
I can see there is some output from |
…any errors that occur will be rendered to the user for troubleshooting. Use --quiet on 'git rm' to suppress non-error output. Fixes #275 until the error happens again.
JFYI |
Also, this happens to untracked files (not $ touch some_file
$ git rm -f some_file
fatal: pathspec 'some_file' did not match any files
$ echo $?
128 |
The original error I hit was during git add. |
|
I'm attempting to use blurb for the first time, but right off the bat, I'm getting a CalledProcessError:
The text was updated successfully, but these errors were encountered: