Serhii Shymkiv

My case was fixed with: ```shell bits-ui ^0.15.1 → ^0.16.0 vaul-svelte ^0.1.0 → ^0.2.1 ``` Thank you.

> My case was fixed with: > > ```shell > bits-ui ^0.15.1 → ^0.16.0 > vaul-svelte ^0.1.0 → ^0.2.1 > ``` > > Thank you. Issue is back again with:...

In my case `` does not help. I unfortunately had no time to dig into this issue.

The `UND_ERR_SOCKET` is typically related to lower-level network communication issues in `Node.js` environments. This suggests that the problem is occurring at the network connection level rather than being an issue...

Closing for now.

It does not happen again...

Still no signs of the issue, it seems the root cause was on the GitHub Actions (linux VMs) side.

Although it might be related to https://github.com/o1-labs/zkapp-cli/pull/658. In which case we need to updated all the `localhost` entries in `o1js` GitHub repo with the explicit **IPv4** `127.0.0.1` reference.

> If so, it would be great if we could move all the updates with these urls to another PR and merge them before HF. Actually let me update network...

[Internal discussion](https://o1-labs.slack.com/archives/C028Q27R8UC/p1712575516480379).