`NamedPipeServerStream` recieves empty string from client
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- operating-systems
Research direction
Start by running the reproduction repository at https://github.com/U-C-S/NamedPipesWindows-IssueRepro and observe the first request after startup. Trace the Rust client and System.IO.Pipes.NamedPipeServerStream interaction to determine why StreamReader receives an empty string; done means the server consistently receives the client’s non-empty string on the stated Windows configuration.
Written by the indexing model from the issue text.
Description
Description
When a named pipe client sends a string, System.IO.Pipes.NamedPipeServerStream in my application sometimes, usually the first request after application started running, gets it as a empty string "" from the StreamReader.
Reproduction Steps
Created a repository to reproduce the issue. Note that my client is written in Rust.
https://github.com/U-C-S/NamedPipesWindows-IssueRepro
Expected behavior
Named Pipe Server should get the string from client as it is, on all occasions.
Actual behavior
Named Pipe Server gets an empty string occasionally from client, even when client certainly is sending a non-empty string, usually on first launch of the application the server is part of.
Regression?
No response
Known Workarounds
No response
Configuration
- .NET SDK version:
8.0.404 - OS and version:
Windows 11 stable build 26100.3194 - architecture: x64
- Do you know whether it is specific to that configuration? - No
Other information
No response
- Dominant language
- C#
- Stars
- 18.3k
- Forks
- 5.6k
- PR merge metrics
- PR metrics pending
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dotnet/runtime
-
agentic-workflows untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
area-System.Reflection blocking-clean-ci-optional Known Build Error os-mac-os-x untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
area-CodeGen-coreclr untriaged
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
agentic-workflows untriaged
Difficulty 1/5 Under an hour Newbie friendliness 78/100
-
area-VM-meta-mono untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
:watch: Not Triaged 11.0 fundamentals/subsvc
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
dotnet/AspNetCore.Docs#37699 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SubtitleEdit/subtitleedit#15108 · 1 comment ·
-
area/docs-content Bug pulumi/docs
Difficulty 1/5 1-3 hours Newbie friendliness 94/100
-
Create parent directories only after the containment check in InstallHelper.TryExtractToDirectory Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
PowerShell/PSResourceGet#2056 ·