Updating sandbox connection status

[dgolovin]

Update connection status every 2 seconds.

[dgolovin]

@benoitf How do we usually deal with dependency cycles? The only way I found is intercept warnings and cancel it.

[benoitf]

@dgolovin usually we avoid these situations by refactoring the code

[dgolovin]

@benoitf well, I have only one file in the extension, but whenever I use Kubeconfig from @kubernetes/client-node I get this locally and that fails the build on macOS.

% yarn build
yarn run v1.22.19
warning redhat-sandbox@0.0.1: The engine "podman-desktop" appears to be invalid.
$ rollup --bundleConfigAsCjs --config rollup.config.js --compact --environment BUILD:production  && node ./scripts/build.js

src/extension.ts → dist...
(!) Circular dependencies
node_modules/sshpk/lib/key.js -> node_modules/sshpk/lib/fingerprint.js -> node_modules/sshpk/lib/key.js
node_modules/sshpk/lib/fingerprint.js -> node_modules/sshpk/lib/private-key.js -> node_modules/sshpk/lib/fingerprint.js
node_modules/sshpk/lib/private-key.js -> node_modules/sshpk/lib/signature.js -> node_modules/sshpk/lib/utils.js -> node_modules/sshpk/lib/private-key.js
...and 89 more
created dist in 6.4s
✨  Done in 25.59s.

Will try to apply what is suggested here TritonDataCenter/node-sshpk#42

[dgolovin]

This seems to happen only to external dependencies, because in case of extensions in podman-desktop repository it is not present in extension's node_modules folder.

[benoitf]

you could use vite instead of roll-up as in the compose extension