Skip to content
This repository has been archived by the owner on Dec 22, 2021. It is now read-only.

Driver doesn't fail fast when connecting to wrong eventstore node port. #104

Open
YoEight opened this issue Sep 3, 2019 · 0 comments
Open
Labels

Comments

@YoEight
Copy link
Owner

YoEight commented Sep 3, 2019

It looks like the driver doesn't even care. Easy step to reproduce, try to connect to internal HTTP port of an eventstore node. It should close connection fast but instead, the driver keeps ticking without updating its internal state at any point.

@YoEight YoEight added the bug label Sep 3, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant