Skip to content

Conversation

@victorgp
Copy link

Rigth now only the word "fatal:" is being checked but there are also errors that start with "error:", for example:

$ git pull origin master
From github.host.com/mycompany/repo

  • branch master -> FETCH_HEAD
    Updating 49d7506..7de461c
    error: Your local changes to the following files would be overwritten by merge:
    mydir/myfile.txt
    Please, commit your changes or stash them before you can merge.
    Aborting

@ByronByron added this to the v1.0.2 - Fixes milestone Jun 10, 2015
@ByronByron self-assigned this Jun 10, 2015
@ByronByron merged commit 3e79604 into gitpython-developers:masterJun 10, 2015
Byron added a commit that referenced this pull request Jun 10, 2015
Reverted changes of `fe2fbc5~2`. This caused `git-pull` to error, which now actually results in a fatal error while fetching or pulling. Previously we simply didn't check for this issue. Now we are back to a `poll` based or threaded concurrent reading from stdout and stderr to prevent a git process deadlock, and the aforementioned error. Related to #297
@Byron
Copy link
Member

Thank you ! This actually caused a 'sleeping' issue to show itself, which is now fixed as well. Of course I can only hope this doesn't cause breakage elsewhere, but at least the test-suite is happy with it.

@Byron
Copy link
Member

You can watch the development stream on youtube.

GitPython #6 [merge PR 297 - uncover and fix a latent bug]

thumb

@victorgp
Copy link
Author

Thanks! Great that i found that latent bug ;)

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@victorgp@Byron