-
Notifications
You must be signed in to change notification settings - Fork 17
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
close failed in file object destructor #76
Comments
It's only on one system, so far as I can tell. I've tried installing a SIGPIPE handler, exception handlers and a sys.excepthook, and none catch the problem. Stumped. |
P.S. It's just a nuisance: the repo is successfully cloned. |
I thought I had fixed this error a long time ago. I believe it has something to do with gitifyhg trying to send data into the git pipe after git has closed the pipe. It must be some kind of race condition, but as you say, it seems to be benign. |
A strange error is appended to the usual clone output. No further information is available using
DEBUG_GITIFYHG
. Might it be related to reopening stdout unbuffered?The text was updated successfully, but these errors were encountered: