Skip to content

Conversation

stgraber
Copy link
Member

Non-interactive exec sessions need all 4 websockets connected within the timeout. Those are typically connected sequentially, so the 5s timeout may be tight on very high latency links.

Non-interactive exec sessions need all 4 websockets connected within the
timeout. Those are typically connected sequentially, so the 5s timeout
may be tight on very high latency links.

Signed-off-by: Stéphane Graber <stgraber@stgraber.org>
@Gurpartap
Copy link

Is this timeout in incus-agent related?

// As this function only gets called when the exec request has WaitForWS enabled, we expect the client to
// connect to all of the required websockets within a short period of time and we won't proceed until then.
logger.Debug("Waiting for exec websockets to connect")
select {
case <-s.requiredConnectedCtx.Done():
break
case <-time.After(time.Second * 5):
return errors.New("Timed out waiting for websockets to connect")
}

@hallyn hallyn merged commit ae0e7ec into lxc:main Aug 22, 2025
34 of 38 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants