Skip to content

[EventPipe][UserEvents] Allow empty tracepoint sets#119651

Merged
mdh1418 merged 1 commit intodotnet:mainfrom
mdh1418:fix_user_events_empty_tracepoint_sets
Sep 12, 2025
Merged

[EventPipe][UserEvents] Allow empty tracepoint sets#119651
mdh1418 merged 1 commit intodotnet:mainfrom
mdh1418:fix_user_events_empty_tracepoint_sets

Conversation

@mdh1418
Copy link
Member

@mdh1418 mdh1418 commented Sep 12, 2025

When enabling a user_events-based eventpipe session, its valid for the tracepoint_sets to be empty if there is a default_tracepoint_name.

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR allows empty tracepoint sets when enabling user_events-based EventPipe sessions, provided a default tracepoint name is specified. The change modifies the validation logic to accept empty tracepoint sets as valid input.

  • Fixed validation logic to allow empty tracepoint sets when appropriate

@mdh1418 mdh1418 merged commit ba2f2d7 into dotnet:main Sep 12, 2025
130 of 132 checks passed
@mdh1418
Copy link
Member Author

mdh1418 commented Sep 12, 2025

/backport to release/10.0

@github-actions
Copy link
Contributor

@github-actions github-actions bot locked and limited conversation to collaborators Oct 13, 2025
@mdh1418 mdh1418 deleted the fix_user_events_empty_tracepoint_sets branch November 26, 2025 16:57
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants