-
When errors are involved in the cloning process, the clone_from() method doesn't preserve the original error message, instead it shows an exit code only. |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments
-
I don't think this is true:
For information on how to use GitPython, there is plenty of documentation on how to do the basics. |
Beta Was this translation helpful? Give feedback.
-
Please add as argument the Progress() class defined here and try again. Stderr gets lost. |
Beta Was this translation helpful? Give feedback.
-
In that case one will have to parse stderr yourself, as it's now passed to the progress. My comment below applies to catch potential errors while progress is handled. |
Beta Was this translation helpful? Give feedback.
-
Unfortunately overriding the line_dropped() didn't help, I think there's much to modify in that util.py. By the way, it's weird that if we the ask the clone_from() to show realtime progresses, it just hides some things, especially ERRORS! I think this can be considered a bug, because in that condition it appears impossible to programmatically handle exceptions. |
Beta Was this translation helpful? Give feedback.
-
Without providing more information on how you tried to intercept Errors are provided on stderr, and so are progress messages. I am sure there is a way to unify the handling so that errors and progress messages are always collected even if progress is collected on top. You are welcome to dig in and improve the situation in a PR. |
Beta Was this translation helpful? Give feedback.
Without providing more information on how you tried to intercept
line_dropped()
calls, there is no way to tell why it didn't work for you.Errors are provided on stderr, and so are progress messages. I am sure there is a way to unify the handling so that errors and progress messages are always collected even if progress is collected on top.
You are welcome to dig in and improve the situation in a PR.