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
Git Tfs unshelve returns the error "A shelved pending change on a file is required: path\to\file" #419
Comments
Make it |
Or |
@vitalybe What's the status of this? I'm experiencing the same problem. |
@Kazark I made a fix in the code to make it happen, but never matured it enough for a PR... I am not really sure I have that code now. So my best suggestion to you would be to run "git tfs" via Visual Studio and add that exception handling ad-hoc. If you can a PR that'd be even better :) |
I don't have it anymore, sorry |
@spraints I should have left myself a better paper trail on this. It has been long enough with enough life events in between that even though I am sure there are still shelfsets out there that would do it for me I don't know which ones they are. :( 😦 If I get a chance I could look around... |
@spraints Today I run in this issue. I try this fix, but it didn't help. Here is a log
I change https://github.com/spraints/git-tfs/blob/ignore-unshelve-errors/GitTfs/Core/TfsChangeset.cs#L35 to: ignorableErrorHandler.Catch(() => _changeset.Get(workspace, sieve.GetChangesToFetch())); this seems to help. But I'm not sure if it correct, so here is a log:
|
@idealist1508 - That'll cancel the |
Thanks, It works. |
@spraints can we re-open this, as although you can now get the rest of the shelveset I'm losing the deletion of a folder when retrieving a shelved change. Current trace:
|
In my case it happens when a folder is deleted in a shelve.
It seems that the error comes from TFS and there isn't much Git TFS can do about it. However, I thought to add a "--ignore-errors" flag that will basically try-catch-log specific unshelve errors, show them in the output, but won't cancel the unshelve process.
What are your thoughts on this?
The text was updated successfully, but these errors were encountered: