You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Panicking on initialization due to a single connection error would be extremely weird behavior. go-redis establishes connections lazily on-demand when commands are issued, and any connection errors are correctly surfaced there. If you want to ensure that a connection is valid after creating a client, consider issuing a Ping immediately, and panicking at your application layer if that fails.
Issue tracker is used for reporting bugs and discussing new features. Please use
stackoverflow for supporting issues.
newClient should panic when failed to connect to a db
Expected Behavior
panic when failed to connect to a db
Current Behavior
nothing happened
Possible Solution
panic when failed to connect to a db
Steps to Reproduce
Context (Environment)
it leaves init error to runtime error
newClient should panic when failed to connect to a db
Detailed Description
Possible Implementation
The text was updated successfully, but these errors were encountered: