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
I am getting "publish was broken by timeout" on approximately 10% of publish calls with the latest master.
It appears that this is due to PR #326 which calls time.After(c.options.WriteTimeout) (client.go:604). If WriteTimeout is 0 (the default) then its possible that both options in the select statement will be ready so one will be chosen at random. Unfortunately when this happens the publish message is lost (I do not have code to deal with that because it should not be necessary with the filestore enabled).
The text was updated successfully, but these errors were encountered:
I am getting "publish was broken by timeout" on approximately 10% of publish calls with the latest master.
It appears that this is due to PR #326 which calls
time.After(c.options.WriteTimeout)
(client.go:604). If WriteTimeout is 0 (the default) then its possible that both options in the select statement will be ready so one will be chosen at random. Unfortunately when this happens the publish message is lost (I do not have code to deal with that because it should not be necessary with the filestore enabled).The text was updated successfully, but these errors were encountered: