[BUG]: Make websocket connection timeout configurable

[maxammann]

Describe the bug

The Zoo cli uses the kcl-lib to connect to server infrastructure. For very long tasks it can be relevant to allow a longer timeout than 60 seconds.

The 60s timeout is configured here:

modeling-app/src/wasm-lib/kcl/src/engine/conn.rs

Line 495 in e0de049

while current_time.elapsed().as_secs() < 60 {

Steps to Reproduce

1. Do zoo kcl snapshot
2. Observe that after 60 seconds the timeout is hit.

Expected Behavior

Make the timeout configurable.

Screenshots and Recordings

No response

Desktop OS

Linux

Browser

No response

Version

any

Additional Context

No response

[maxammann]

This issue is also relevant for other projects.

[franknoirot]

Do you need any support on this effort @maxammann? I am unclear why this is marked as a bug, as making something configurable seems like an enhancement to me?

[maxammann]

I guess you are right. The reason why I marked this as a but is because it was blocking me. A modeling command can take more than 60 seconds in worst cases, e.g. during backend initialization.

So the fact that it is hard coded is close to being a bug.

[maxammann]

Also see the referenced PR

[franknoirot]

Yeah totally fair, you're right. This shouldn't be too hard to weave through as a new CLI arg

[jtran]

The timeout was increased here:

• bump the client API response timeout 60 -> 300 #7406

[jtran]

I found a very similar timeout in another place.

modeling-app/rust/kcl-lib/src/engine/mod.rs

Line 270 in 383b38c

while current_time.elapsed().as_secs() < 60 {