Open iliesh opened 10 months ago
Thanks for the issue. As you said It needs to reconnect after the websocket connection is broken after other PRs merged I will look into this.
We do want a shared configuration between drivers about how we handle network traffic (timeouts, reconnects, circuiting breaking strategies etc). Overall this would need to be standardised but for now we could add a helper.
Would recommend adhering to existing golang standards.
Describe the bug
When the application is running, and the DB is restarted, then the application panic with the following stack:
Steps to reproduce
run an application and then stop surrealdb
Expected behaviour
reconnect or return back an error to the application, and let developer decide what to do
SurrealDB version
1.0.0+20230913.54aedcd for linux on x86_64
Contact Details
iliusha.md@gmail.com
Is there an existing issue for this?
Code of Conduct