Skip to content
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

.NET core sdk is still SPYING it's users even after it's "disabled" by "DOTNET_CLI_TELEMETRY_OPTOUT=1" environment variable #12841

Closed
unavaliabl3 opened this issue Aug 9, 2020 · 2 comments

Comments

@unavaliabl3
Copy link

unavaliabl3 commented Aug 9, 2020

My dotnet sdk is extremely slow on creating new projects, so I dug a little on this abnormal behavior, and then I found that dotnet is making a lot of network requests. I use Wireshark captured those activities:

.NET core sdk sends requests to

go.microsoft.com:443
nam06.safelinks.protection.outlook.com:443
webpifeed.blob.core.windows.net:443
blob.byaprdstr14a.store.core.windows.net:443

when "dotnet new" runs.

Dotnet sdk won't return to the shell before those requests finished, and that's why it hangs after "Restore succeeded." message

Not a new thing: #6145
But I already set DOTNET_CLI_TELEMETRY_OPTOUT=1 on my machine

@dagood
Copy link
Member

dagood commented Aug 10, 2020

This set of hosts looks like dotnet new checking for template updates, rather than telemetry. #10564

Maybe you can set DOTNET_NEW_LOCAL_SEARCH_FILE_ONLY=1 and try again to try to rule that out? I found it in dotnet/templating#2093, which tracks improvements around the slowdown.

@unavaliabl3
Copy link
Author

Sorry, hit a wrong thing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants