-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
When auth fails during nuget stats, render failure #363
Conversation
It can be helpful to see the actual error from the GH CLI when authentication fails. We only propagate the error as the output to the caller from our process helper if there was no output already (i.e. some graphql APIs return failure but still provide data). This eliminates the chance of breaking existing code that relied on that. Also added a debug-only option to pass in a direct token, which is easier for debug runs of the CLI.
🧪 Details on macOS Unix 14.6.1✅ Devlooped.Tests.SponsorLinkTests.TryRead 🧪 Details on Ubuntu 22.04.5 LTS✅ Devlooped.Tests.SponsorLinkTests.TryRead 🧪 Details on Microsoft Windows 10.0.20348✅ Devlooped.Tests.SponsorLinkTests.TryRead from dotnet-retest v0.6.3 on .NET 8.0.8 with 💜 |
It can be helpful to see the actual error from the GH CLI when authentication fails. We only propagate the error as the output to the caller from our process helper if there was no output already (i.e. some graphql APIs return failure but still provide data). This eliminates the chance of breaking existing code that relied on that.
Also added a debug-only option to pass in a direct token, which is easier for debug runs of the CLI.