jsk

+1 I am seeing this hang at gulpfile.js creation as well. Node is 100% CPU.

I ran into this as well. darosio's fix didn't work at first. I had to delete the `.emacs.d/org-cal/.org-gcal-token` and then eval'd `(org-gcal-request-token)` which worked.

I am using node.js as the backend if that wasn't clear. Thanks!

~Experiencing this as well~ Actually, I posted too soon. I _was_ experiencing this but put the project on hold for a week. I just tried and now kafka is staying...

Curious if others in this thread are now running into an issue where updating the Launcher from 0.20 to 0.21 completes successfully but doesn't actually update, staying at 0.20. Reported...

Setting `key length` to `4096` also fixed the issue for me. With TLS w/ 2048 keys enabled, I never was able to establish a connection. (Check your TLS settings, time...

Perhaps relevant context, I ran into an error last time I updated ([unknown flag: --update-devbox-symlink]( https://github.com/jetpack-io/devbox/issues/1616#issue-1986424655)), so perhaps something was missed there and put me in this state.

The 'latest' version still throws this error for me: ``` $ devbox version -v Version: 0.10.2 Platform: darwin_arm64 Commit: 63981b041029d9eb2288f26e39dc6b4fce81eca1 Commit Time: 2024-03-28T20:26:27Z Go Version: go1.22.1 Launcher: 0.2.1 ``` ```shell...

> What's weird is this works fine in iTerm but it fails in Terminal.app and Alacritty. Tested on devbox 0.10.7 That's strange. Fwiw, I was using kitty on macos.

Was running into a similar issue between Mac (client) and Windows (server). Same TLS settings pop up and `timed out` connection errors in log. From #8040, a poster had suggested...