Skip to content

Conversation

@baronfel
Copy link
Member

@baronfel baronfel commented Jul 30, 2024

Fixes azdo#2174440

Context

The serialization of telemetry events assumed that telemetry properties would always have a value - it seems like it's possible for callers to send null values, so we need to be able to handle that. This was triggered with the addition of containers telemetry added in 8.0.400.

Changes Made

Optionally write and read the value string for the telemetry event payload.

Testing

Added previously-nonexistent round-tripping tests for this event type.

Notes

We'll want to take this to SDK Tactics for servicing, but then to VS QB to see if they want to align releases or let the VS side drift a bit.

@rainersigwald rainersigwald requested a review from a team as a code owner July 30, 2024 21:17
@baronfel baronfel force-pushed the fix-telemetry-event-serialization branch from 3b07965 to 036459b Compare July 30, 2024 22:29
@baronfel baronfel changed the title Telemetry strings could be null, so handle that case Fix serialization of TelemetryEventArgs data packets across MSBuild worker nodes Aug 1, 2024
@baronfel baronfel changed the title Fix serialization of TelemetryEventArgs data packets across MSBuild worker nodes [8.0.4xx] Fix serialization of TelemetryEventArgs data packets across MSBuild worker nodes Aug 1, 2024
@MichalPavlik MichalPavlik merged commit 37eb419 into vs17.11 Aug 6, 2024
@MichalPavlik MichalPavlik deleted the fix-telemetry-event-serialization branch August 6, 2024 14:34
@MichalPavlik MichalPavlik restored the fix-telemetry-event-serialization branch August 6, 2024 14:34
@baronfel baronfel deleted the fix-telemetry-event-serialization branch August 6, 2024 15:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants