Skip to content

remote.pull losing info for error message #448

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

Closed
barry-scott opened this issue May 28, 2016 · 5 comments
Closed

remote.pull losing info for error message #448

barry-scott opened this issue May 28, 2016 · 5 comments

Comments

@barry-scott
Copy link
Contributor

When a pull cannot merge the changes it reports a list of files after the
error message. I need that list in my app to show the user.

I suggest that after seeing the error: line in the output that you collect up the following lines
and add them to the GitCommand error.

The change would be made in remote.py _get_fetch_info_from_stderr.

Also does the raise prevent the sub process from being shutdown completely?

@Byron Byron self-assigned this May 28, 2016
@Byron
Copy link
Member

Byron commented May 28, 2016

I think it's very possible that the process is left hanging, just as finalize process is not called. That should definitely be fixed, in any case.

With such a fix, it should be relatively easy to provide the remaining information provided by the git process in the GitCommandError instance. As mentioned, this would be done here.

Now as you already have some experience with the codebase and the software to test it, I believe you would be the one to find a nice and suitable API for this kind of issue.

What's your opinion about it ?

@barry-scott
Copy link
Contributor Author

Looks like the API exists GitCommandError has a stderr arg that looks like it is for this purpose.

I'm creating a PR for this problem.

@barry-scott
Copy link
Contributor Author

PR in your queue for review.

@Byron Byron removed their assignment Jul 23, 2016
@Byron
Copy link
Member

Byron commented Aug 3, 2016

@barry-scott Is this one already fixed by the PR mentioned here ? Unfortunately it is not linked, so I am a little lost on this one.

@barry-scott
Copy link
Contributor Author

Yes it is fixed enough to close. Really needs that cmd rewrite to be clean.

Barry

On 3 Aug 2016, at 04:31, Sebastian Thiel [email protected] wrote:

@barry-scott Is this one already fixed by the PR mentioned here ? Unfortunately it is not linked, so I am a little lost on this one.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@Byron Byron closed this as completed Aug 4, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants