Skip to content

Clarify that DataReceivedEventArgs.Data is null at end of stream#12657

Draft
Copilot wants to merge 2 commits into
mainfrom
copilot/fix-final-newline-detection
Draft

Clarify that DataReceivedEventArgs.Data is null at end of stream#12657
Copilot wants to merge 2 commits into
mainfrom
copilot/fix-final-newline-detection

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented May 25, 2026

Process.OutputDataReceived/ErrorDataReceived raise a final event with Data == null when the redirected stream closes, but this wasn't clearly documented—making it impossible to distinguish "no trailing newline" from "end of stream" without reading the source.

  • Updated DataReceivedEventArgs.Data <value> to state the property is null at end of stream
  • Added explicit paragraph to both OutputDataReceived and ErrorDataReceived remarks noting the null-data end-of-stream signal

Copilot AI changed the title [WIP] Fix final newline detection in OutputDataReceived Clarify that DataReceivedEventArgs.Data is null at end of stream May 25, 2026
Copilot AI requested a review from adamsitnik May 25, 2026 17:24
@github-actions github-actions Bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label May 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners

Projects

None yet

Development

Successfully merging this pull request may close these issues.

System.Diagnostics.Process.OutputDataReceived - determine final newline

2 participants