{"action":"created","issue":{"url":"https://api.github.com/repos/projectkudu/kudu/issues/2664","repository_url":"https://api.github.com/repos/projectkudu/kudu","labels_url":"https://api.github.com/repos/projectkudu/kudu/issues/2664/labels{/name}","comments_url":"https://api.github.com/repos/projectkudu/kudu/issues/2664/comments","events_url":"https://api.github.com/repos/projectkudu/kudu/issues/2664/events","html_url":"https://github.com/projectkudu/kudu/issues/2664","id":288940372,"node_id":"MDU6SXNzdWUyODg5NDAzNzI=","number":2664,"title":"Can no longer push to remote git repo in Azure App Service Editor (preview)","user":{"login":"jk-ncsc","id":29426421,"node_id":"MDQ6VXNlcjI5NDI2NDIx","avatar_url":"https://avatars1.githubusercontent.com/u/29426421?v=4","gravatar_id":"","url":"https://api.github.com/users/jk-ncsc","html_url":"https://github.com/jk-ncsc","followers_url":"https://api.github.com/users/jk-ncsc/followers","following_url":"https://api.github.com/users/jk-ncsc/following{/other_user}","gists_url":"https://api.github.com/users/jk-ncsc/gists{/gist_id}","starred_url":"https://api.github.com/users/jk-ncsc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jk-ncsc/subscriptions","organizations_url":"https://api.github.com/users/jk-ncsc/orgs","repos_url":"https://api.github.com/users/jk-ncsc/repos","events_url":"https://api.github.com/users/jk-ncsc/events{/privacy}","received_events_url":"https://api.github.com/users/jk-ncsc/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":20,"created_at":"2018-01-16T15:08:58Z","updated_at":"2018-06-04T22:40:48Z","closed_at":null,"author_association":"NONE","body":"The issue is that I'm no longer able to \"push\" to a remote Git repo from Azure App Service Editor or Kudu console.\r\n\r\nI started this by outlining _my_ specific error, then realised this happens even on a new and empty Web App.... so I've tried to make the repro below as generic as I can:\r\n\r\n### Repro from Blank\r\n\r\n* Create a new github repo (e.g. https://github.com/jk-ncsc/testing-ASE)\r\n* Create a new Web App in Azure (Free Tier - F1, B1 also tested) (e.g. \"testing-ase[.]azurewebsites[.]net\")\r\n* Open \"App Service Editor (preview)\" in WebApp options\r\n* Select \"Git\" section and add a git repo (sync works fine)\r\n* Make a change (e.g. add a file)\r\n* Select \"Git\" section and commit change with a message (success)\r\n* Select \"Git\" dropdown and select \"push\" (hangs a while then errors, blank message in UI)\r\n* Developer tools error message is \"There was an issue running a git operation. Please use the console to check the state of your repository.\" (same on latest Chrome & Edge)\r\n* Open console, check \"git status\" and then do a\"git push\" (fails)\r\n* In this example, it just hangs, with no output\r\n* I had the following explicit output on my main projects (both api apps give same errors)\r\n```\r\nerror: cannot create standard input pipe for git credential-manager get: Function not implemented\r\nerror: cannot create standard input pipe for \"$HOME/bin/cred.sh\" get: Function not implemented\r\nerror: cannot create standard output pipe for D:\\home\\data\\monaco\\home\\empty.cmd: Function not implemented\r\nerror: cannot create standard input pipe for bash: Function not implemented\r\nfatal: could not read Password for 'https://<USERNAME>@bitbucket.org/<NAME>/<PROJECT>.git': Function not implemented\r\n```\r\nI've been using the ASE for months successfully. Last successful push was 17th Dec I think!"},"comment":{"url":"https://api.github.com/repos/projectkudu/kudu/issues/comments/394523323","html_url":"https://github.com/projectkudu/kudu/issues/2664#issuecomment-394523323","issue_url":"https://api.github.com/repos/projectkudu/kudu/issues/2664","id":394523323,"node_id":"MDEyOklzc3VlQ29tbWVudDM5NDUyMzMyMw==","user":{"login":"suwatch","id":1088218,"node_id":"MDQ6VXNlcjEwODgyMTg=","avatar_url":"https://avatars3.githubusercontent.com/u/1088218?v=4","gravatar_id":"","url":"https://api.github.com/users/suwatch","html_url":"https://github.com/suwatch","followers_url":"https://api.github.com/users/suwatch/followers","following_url":"https://api.github.com/users/suwatch/following{/other_user}","gists_url":"https://api.github.com/users/suwatch/gists{/gist_id}","starred_url":"https://api.github.com/users/suwatch/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/suwatch/subscriptions","organizations_url":"https://api.github.com/users/suwatch/orgs","repos_url":"https://api.github.com/users/suwatch/repos","events_url":"https://api.github.com/users/suwatch/events{/privacy}","received_events_url":"https://api.github.com/users/suwatch/received_events","type":"User","site_admin":false},"created_at":"2018-06-04T22:40:48Z","updated_at":"2018-06-04T22:40:48Z","author_association":"MEMBER","body":"The cred hook is done thru `credential.helper`.    App Service Editor adds this config in webapp's `D:\\home\\data\\monaco\\home\\.gitconfig`.   \r\n```\r\n\\ [master]> git config --global --list\r\n...\r\ncredential.helper=!\"$HOME/bin/cred.sh\"\r\n```\r\n\r\nThe $HOME points to App Service Editor's home which is `d:\\Program Files (x86)\\SiteExtensions\\Monaco\\1.0.0-20180530\\server\\home`.   The issue seems to be the [git-credential-manager](https://github.com/Microsoft/Git-Credential-Manager-for-Windows/issues/649) does not take `credential.helper` as precedent over its built in auths for GitHub\\Bitbucket\\.. etc.   If I remove either git-credential-manager.exe or GitHub.Authentication.exe from `d:\\Program Files (x86)\\Git\\mingw32\\libexec\\git-core`, then credential.helper will kick it.  We are checking with dev owning to see what is the cleaner way and why it was working before. \r\n\r\n\r\n"}}
{"actor":{"display_login":"suwatch"}}