Oliver Mannion
Oliver Mannion
I see.. so that will avoid the error during deletion, but would that still allow two concurrent actions to receive the same message? To avoid that I guess I need...
So I think I've found a case where the action is triggered more than max_action times. When I run this [fizz file](https://gist.github.com/tekumara/162453b7546c981052437f58d3ab5abf) the `Human#0.Input` action crashes twice and then runs...
Also have installed Docker Desktop 4.19 and no docker cli tool symlinks are present in _/usr/local/bin_ or _~/.docker/bin_ I have Advanced -> System checked: In the logs I see: ```...
FYI - I installed Docker Desktop on a machine that previously had docker desktop installed. On first open, I was not presented with this Finish setting up Docker Desktop dialog:...
To install the docker CLI symlinks into _/usr/local/bin_ I did the following: 1. Navigate to `Settings -> Advanced` 1. Check `User` and `Click Apply & Restart` 1. When osascript asks:...
[Remote-SSH Bug]: failed to connect with setting "remote.SSH.defaultExtensions" and profile function
Still happening in 1.94.2 ... On the first connect after opening VS Code its fine: ``` [22:08:09.930] [server] [11:08:09] Installing extensions... [22:08:09.944] [server] [11:08:09] Extension host agent started. [22:08:10.099] [server]...
[Remote-SSH Bug]: failed to connect with setting "remote.SSH.defaultExtensions" and profile function
Removing the symlinked _~/.vscode-server_ directory (which pointed to an NFS mount) and re-connecting has fixed this: ``` rm -rf ~/.vscode-server/ ```
[Remote-SSH Bug]: failed to connect with setting "remote.SSH.defaultExtensions" and profile function
@joshspicer is the ~/.vscode-server-insiders/ directory on your remote machine a symlink? I can only repro this on 1.9.4.2 when its a symlink (I've yet to try the latest insiders version)
[Remote-SSH Bug]: failed to connect with setting "remote.SSH.defaultExtensions" and profile function
@joshspicer I've tried this with the ~/.vscode-server symlink and vscode 1.95.1 and it appears to now work - thank you!
> Since it is set to a max of twice, this deadlock happens. Because it was called twice in the stack trace. I thought with [this change](https://github.com/fizzbee-io/fizzbee/issues/91#issuecomment-2396221050) if max_actions is...