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
In the new Vault Token Wrapper code it reuses the runner's done channel to know when to close, but only takes the done channel to avoid a circular import issue. But the vault token watcher setup call is before the done channel gets initialized, so it is passed as a nil channel (and thus just always blocks).
Need to move the initialization of the channel above its use.
Note that this will cause gouroutine leaks on config reloads when it starts/stops a new runner.
The text was updated successfully, but these errors were encountered:
In the new Vault Token Wrapper code it reuses the runner's done channel to know when to close, but only takes the done channel to avoid a circular import issue. But the vault token watcher setup call is before the done channel gets initialized, so it is passed as a nil channel (and thus just always blocks).
Need to move the initialization of the channel above its use.
Note that this will cause gouroutine leaks on config reloads when it starts/stops a new runner.
The text was updated successfully, but these errors were encountered: