don't sent dotnet telemetry #9614
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
JamieMagee
approved these changes
Apr 25, 2024
|
@JamieMagee that second issue won't be closed by this, it's been running on my machine for 4 hours now, but the first one might. |
raj-meka
force-pushed
the
dev/brettfo/no-dotnet-telemetry
branch
from
3c94e53
to
e9b234e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
dotnetCLI by default sends a bunch of telemetry that's not necessary (and isn't really what they're looking for anyway.) It shows up in the log as a bunch ofPOSTrequests tohttps://dc.services.visualstudio.com/v2/track. Setting an environment variable turns this off. I've confirmed this change locally.