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
rust client has a timout on the unix socket connection (of configurable length) which allows the client application to recover (i.e. detect failure and compensate if possible) if the parsec daemon is not responding. Go client needs same functionality - default of 1s likely sensible.
The text was updated successfully, but these errors were encountered:
For dialling, we should be able to use a dialler with a context, having deadline set: https://pkg.go.dev/net#Dialer
For individual reads/writes, we'll have to set deadlines on each read/write for the timeout period - this is ok because the client should only be used single threaded (i.e. one request/response in flight at once), so we'll never get overlapping call windows messing up the deadlines. go doesn't let us set timeouts per read/write, just read and write deadlines on the connection as a whole
rust client has a timout on the unix socket connection (of configurable length) which allows the client application to recover (i.e. detect failure and compensate if possible) if the parsec daemon is not responding. Go client needs same functionality - default of 1s likely sensible.
The text was updated successfully, but these errors were encountered: