-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Add Dev Device ID #43148
Add Dev Device ID #43148
Conversation
Make sure we return an empty string if caching fails but don't error our code refactor the caching code slightly for simplicity
The important points that I checked were:
All of that seems aligned with the spec. |
Failure is the known template engine failure |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed location and implementation based on spec.
Looks correct
Added the documentation label so we don't drop this during the final documentation push. |
/azp run dotnet-sdk-public-ci,sdk-source-build,sdk-unified-build |
Azure Pipelines successfully started running 2 pipeline(s). |
/backport to release/8.0.1xx |
Started backporting to release/8.0.1xx: https://github.com/dotnet/sdk/actions/runs/10816238261 |
/backport to release/8.0.3xx |
Started backporting to release/8.0.3xx: https://github.com/dotnet/sdk/actions/runs/10818712032 |
/backport to release/8.0.4xx |
Started backporting to release/8.0.4xx: https://github.com/dotnet/sdk/actions/runs/10819303900 |
Fixes #42804
I followed the spec for where we should cache the ID from. I confirmed that it was getting populated with a guid in the telemetry common properties and on windows was saved in the cache. This is all assuming I got the locations correct. Ping me offline for the spec and I can link it for review.