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
When setting a timeout through the constructor, the timeout is applied through the watcher as well (since it's sugar over the GET request).
This doesn't make sense. If the etcd directory had no activity within the timeout window, the request module closes the connection (and kicks off the exponential backoff, which means watches could be ridiculously delayed).
If this is intentional, it's easy enough for me to use a workaround and build my own timeout method and avoid the constructor option. If not, I'd be happy to work on a refactoring in a PR that separates out this configuration.
The text was updated successfully, but these errors were encountered:
When setting a timeout through the constructor, the timeout is applied through the watcher as well (since it's sugar over the GET request).
This doesn't make sense. If the etcd directory had no activity within the timeout window, the request module closes the connection (and kicks off the exponential backoff, which means watches could be ridiculously delayed).
If this is intentional, it's easy enough for me to use a workaround and build my own timeout method and avoid the constructor option. If not, I'd be happy to work on a refactoring in a PR that separates out this configuration.
The text was updated successfully, but these errors were encountered: