payload: {"action":"opened","issue":{"url":"https://api.github.com/repos/NuGet/Home/issues/7770","repository_url":"https://api.github.com/repos/NuGet/Home","labels_url":"https://api.github.com/repos/NuGet/Home/issues/7770/labels{/name}","comments_url":"https://api.github.com/repos/NuGet/Home/issues/7770/comments","events_url":"https://api.github.com/repos/NuGet/Home/issues/7770/events","html_url":"https://github.com/NuGet/Home/issues/7770","id":407069052,"node_id":"MDU6SXNzdWU0MDcwNjkwNTI=","number":7770,"title":"Confusing plugins_cache errors, likely long path related","user":{"login":"zarenner","id":13670625,"node_id":"MDQ6VXNlcjEzNjcwNjI1","avatar_url":"https://avatars1.githubusercontent.com/u/13670625?v=4","gravatar_id":"","url":"https://api.github.com/users/zarenner","html_url":"https://github.com/zarenner","followers_url":"https://api.github.com/users/zarenner/followers","following_url":"https://api.github.com/users/zarenner/following{/other_user}","gists_url":"https://api.github.com/users/zarenner/gists{/gist_id}","starred_url":"https://api.github.com/users/zarenner/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/zarenner/subscriptions","organizations_url":"https://api.github.com/users/zarenner/orgs","repos_url":"https://api.github.com/users/zarenner/repos","events_url":"https://api.github.com/users/zarenner/events{/privacy}","received_events_url":"https://api.github.com/users/zarenner/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2019-02-06T03:38:14Z","updated_at":"2019-02-06T03:38:14Z","closed_at":null,"author_association":"NONE","body":"In https://github.com/Microsoft/azure-pipelines-tasks/issues/9446, @maboulianne, @OneCyrus, and @sveinungf all reported an issue with NuGet that appears likely to be due to plugin_cache path lengths being too long (260+ characters).\r\n\r\nPlease see that issue for the full context, but the relevant part:\r\n\r\n> 2019-01-29T12:56:32.0548084Z System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\\Windows\\ServiceProfiles\\NetworkService\\AppData\\Local\\NuGet\\plugins-cache\\7dfd0fa0c00db55241517876f045626154b6f02c$CredentialProvider.Microsoft.exe\\https_comerco.pkgs.visualstudio.com_packaging_ea8caa50-9cf8-4ed7-b410-5bca3b71ec1c_nuget_v3_index.json.dat-new'.\r\n2019-01-29T12:56:32.0548131Z at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)\r\n2019-01-29T12:56:32.0548220Z at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)\r\n2019-01-29T12:56:32.0548267Z at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize)\r\n2019-01-29T12:56:32.0548438Z at NuGet.Protocol.Plugins.PluginCacheEntry.d__20.MoveNext()\r\n2019-01-29T12:56:32.0548476Z --- End of stack trace from previous location where exception was thrown --\r\n\r\nI see that there are already generally related GitHub issues such as #3324.\r\n\r\nHowever, this specific issue is especially bad since the \"DirectoryNotFoundException: Could not find a part of the path\" doesn't hint at the path length being the issue. That's more a .NET issue than a NuGet issue IMO, but it's still a confusing experience for our customers. It's also more likely here to exceed 260 characters here since the plugin_cache paths contain essentially the entire URL, the plugin filename, etc and thus are long.\r\n\r\nEven if NuGet cannot support long paths, could it at least emit a better error message here indicating the issue?"}}
other: {"actor":{"display_login":"zarenner"}}