fix telemetry flow #3054
Merged
fix telemetry flow #3054
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
|
/azp run |
tlmii
approved these changes
Oct 29, 2024
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/backport to release/9.0 |
|
Started backporting to release/9.0: https://github.com/dotnet/Scaffolding/actions/runs/11580361411 |
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.
issue started with first time
dotnet-scaffolduse not detecting any categories, delved deeper and found a bunch of issues.dotnet-scaffold-aspnetanddotnet-scaffold-aspirefirst time sentinel files were being created even when invoked through dotnet-scaffold.TelemetryConstants.DOTNET_SCAFFOLD_TELEMETRY_STATEnot being passed correctly. Passing it in all dotnet invocations now.get-commandsresult