-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RpcException When Using AppendToStreamAsync From Windows #299
Comments
Does this happen constantly? I'm on Windows 11 too and unable to reproduce this error. Which target framework are you on? |
Also worth mentioning whether other operations work etc - i.e. is it simply a firewall-driven timeout due to how your environment is configured? |
I'm not sure about what configuration available. I follow the docker run instruction which use arguments I've tried the read operation Grpc.Core.RpcException: Status(StatusCode="DeadlineExceeded", Detail="") |
This happen constantly. I target .NET 8.0 The project content is below <Project Sdk="Microsoft.NET.Sdk">
<PropertyGroup>
<OutputType>Exe</OutputType>
<TargetFramework>net8.0</TargetFramework>
<ImplicitUsings>enable</ImplicitUsings>
<Nullable>enable</Nullable>
</PropertyGroup>
<ItemGroup>
<PackageReference Include="EventStore.Client.Grpc.Streams" Version="23.2.1" />
</ItemGroup>
</Project> |
Hi @robbytarigan, I have tried this too and have been unable to recreate the problem. Would it be possible for you to provide a small reproducible example via a public GitHub repository? Preferably using docker compose. Thanks in advance! |
I don't think I can reproduce it using docker compose because it does not support mixed windows and linux containers. I even cannot keep the evenstore server running when I switched into windows container. Probably I will need a bit more complex setup to make it reproducible, so need to think different idea. |
@robbytarigan no problem, if it is just the sample you are running as-is then my request for a composable reproducible example likely won't prove useful - I misread the second bullet point in the repro steps and assumed you may have a custom application where you are experiencing the issue, too, my apologies. Regarding Windows vs Linux containers, the Please can you try running the same docker run -d --rm --name esdb-node -it -p 2113:2113 -p 1113:1113 eventstore/eventstore:latest --insecure --run-projections=All --enable-atom-pub-over-http Assuming everything is OK, you should see something like the below: If possible, it would be handy to have a dump of the container/server logs? Healthy or not. |
The eventstore server is healthy. Please see the screenshot below Please also see the server logs attached. |
@robbytarigan Does the event appear in the stream browser? |
@w1am No, the event does not appear |
@robbytarigan I suggest testing a simple operation using a different client, such as the Node.js client or with a different server version (lts). If you continue to encounter the same issue, the problem is likely with your environment. Have you also considered increasing the timeout to see if it makes a difference?
|
@w1am I followed your suggestion to use NodeJS client example, and there is no problem with it. I put the screenshot for this operation here I also try |
@robbytarigan Can you try with this connection string in the dotnet client instead
The difference is that I replaced Remove the previous keepAliveTimeout option I proposed initially |
@w1am I cannot believe it works by replacing localhost with 127.0.0.1. I can see the stream is stored too now. I'll use 127.0.0.1 during local development then. Thank you! |
Describe the bug
RpcException When Using AppendToStreamAsync From Windows.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The stream is appended
Actual behavior
RpcException was thrown with error below:
Config/Logs/Screenshots
The event store server was run using docker with command below
EventStore details
EventStore server version: 24.2.0
Operating system: Windows 11
EventStore client version 23.2.1
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: