Skip to content

Merge main into live - #55198

Open
dotnet-policy-service[bot] wants to merge 5 commits into
livefrom
main
Open

Merge main into live#55198
dotnet-policy-service[bot] wants to merge 5 commits into
livefrom
main

Conversation

@dotnet-policy-service

@dotnet-policy-service dotnet-policy-service Bot commented Jul 31, 2026

Copy link
Copy Markdown
Contributor

azure-sdk-automation Bot and others added 5 commits July 30, 2026 10:34
Co-authored-by: azure-sdk <azuresdk@microsoft.com>
* Document EventPipe buffering mode and Event ID filter client APIs

Add Microsoft.Diagnostics.NETCore.Client reference for EventPipeBufferingMode, EventPipeProviderEventFilter, the new EventPipeSessionConfiguration and EventPipeProvider overloads and properties, and the UnknownCommandException and InvalidCommandArgumentException types.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Document --buffering-mode for dotnet-gcdump and dotnet-trace

dotnet-gcdump collect/report default to non-lossy (Block) with automatic fallback on older runtimes; dotnet-trace collect adds an opt-in --buffering-mode (default Drop). Block requires a .NET 11+ target runtime.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Document non-lossy EventPipe buffering environment variables

Add DOTNET_EventPipeBufferingMode and DOTNET_EventPipeOutputStreaming to the EventPipe environment-variable reference, and note the non-lossy opt-in on the circular-buffer guidance.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Sync buffering-mode docs to latest diagnostics and runtime changes

Remove the --buffering-mode option from dotnet-gcdump (it now always collects non-lossy and falls back to lossy on pre-.NET 11 targets). Replace the dropped UnknownCommandException and InvalidCommandArgumentException with the new BadEncodingException and fix the UnsupportedCommandException base type. Clarify that non-lossy buffering is bounded by buffer capacity and can still drop events under host memory exhaustion or during shutdown, and correct the DOTNET_EventPipeBufferingMode invalid-value and streaming-session behavior.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Fix punctuation in dotnet-gcdump non-lossy buffering note

* Apply suggestions from code review

Co-authored-by: Genevieve Warren <24882762+gewarren@users.noreply.github.com>

---------

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Genevieve Warren <24882762+gewarren@users.noreply.github.com>
@github-advanced-security

Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

@dotnetrepoman dotnetrepoman Bot added this to the July 2026 milestone Jul 31, 2026
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.

4 participants