dotnet/runtime
Ver no GitHub`NamedPipeServerStream` recieves empty string from client
Open
#112.912 aberto em 25 de fev. de 2025
area-System.IOhelp wanted
Métricas do repositório
- Stars
- (17.886 stars)
- Métricas de merge de PR
- (Mesclagem média 12d 11h) (661 fundiu PRs em 30d)
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