![]() Pre-receive hook declined when pushing large number of tags.Error: Unpack Failed: Unpack-objects Abnormal Exit.Can't clone or pull due to a git outbound proxy.error: RPC failed result=22 - Push to Stash fails.Git clone fails with SSL routines:SSL23_GET_SERVER_HELLO.Detached heads are not currently supported.Git push fails - client intended to send too large chunked body.git upload-archive archiver died with error.Git Push fails with 'receive-pack did not complete' error in the logs.error: gnutls_handshake() failed: A TLS warning alert has been received.Repository is not updated by pushing content immediately after its creation.500 errors when opening a file or the commit list when mailmap is used.Git Operations Fail - Permission denied - publickey.Pull Requests Not Reflecting Changes Pushed to Remote Branch After an Upgrade.500 Error Upon Accessing Any Stash Repository.User Configured pre-receive or post-receive Hooks Break After Upgrading Stash.Authentication Fails when Integrating Stash with Github for Windows GUI Client.REMOTE HOST IDENTIFICATION HAS CHANGED when accessing Stash git repo over ssh.Strange Characters in the Author Column for Commits History.Perl validation fails on startup with 'Filename too long' or 'CreateProcess error=267'.Can't access Stash with Git - Issuer certificate is invalid.Stash always shows incorrect Merge Conflict in PRs.Git was not found on the PATH for Stash.Forking JVM: error=12, Cannot allocate memory or error=12, Not enough space.Unable to clone Stash Repository with HTTP transport over haproxy using Windows Git clients.Git Push Fails - fatal: The remote end hung up unexpectedly.Git command returns "not found" or error code 404.I could happily ship #7351 for the next beta to help the users who have encountered problems with their workflow, but I favour the second option to help make this flow less confusing. ![]() be more conservative with the errors detected and inform the user that some paths could not be stashed, giving them the option to continue with whatever could be stashed.use the implementation in handle warnings if stash creation encounters permission issue #7351 and just stash what we can, ignoring the problem paths reported by Git.I updated #7351 to indicate that it shouldn't close this out, and I think we have two options here if we encounter an error: There's some gotchas here (it looks like it creates the stash with the files it could access) but I think that's minor. We actually get this for free from Git - it emits the paths it can't access, and it feels simpler to defer to the actual implementation rather than try and emulate this ourselves. If it turns out permissions would cause stash creation to fail, we can bail and alert the user that we're unable to create a stash due to file permissions and continue with the branch switch as usual. T18:36:44.269Z - error: `git stash push -include-untracked -m !!GitHub_Desktop` exited with an unexpected code: 1. T18:36:44.266Z - info: Executing createStashEntry: git stash push -include-untracked -m !!GitHub_Desktop (took 1.058s) T18:36:24.568Z - info: account found for repository: XXXXXXXXX - xt0rted (has token) T18:36:10.307Z - info: Executing popStashEntry: git stash pop (took 1.183s) T18:36:08.476Z - info: account found for repository: XXXXXXXXX - xt0rted (has token) T18:36:08.475Z - info: Executing createStashEntry: git stash push -include-untracked -m !!GitHub_Desktop (took 1.826s) OnSubmit stash-and-switch-branch-dialog.tsx:126 Uncaught (in promise) p: warning: failed to remove docs/Report 04092019.pdf: Invalid argumentĪt Object.t.git (file:///C:/Users/brian/AppData/Local/GitHubDesktop/app-1.7.0-beta4/resources/app/renderer.js:5:7806)Īt process._tickCallback (internal/process/next_tick.js:68:7) ![]() InvokeGuardedCallbackAndCatchFirstError :16īatchedUpdates :187 OnSubmit stash-and-switch-branch-dialog.tsx:150 StashAndCheckout stash-and-switch-branch-dialog.tsx:170 ![]() _tickCallback internal/process/next_tick.js:68 Warning: failed to remove docs/Report 04092019.pdf: Invalid argument Saved working directory and index state On master: !!GitHub_Desktop Install.ts:23 `git stash push -include-untracked -m !!GitHub_Desktop` exited with an unexpected code: 1.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |