You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried to launch a devcontainer of https://github.com/moby/moby project and attach to it, but failed with error
Error executing luv callback:
vim/_editor.lua:0: E5560: nvim_err_writeln must not be called in a lua loop callback
stack traceback:
[C]: in function 'nvim_err_writeln'
vim/_editor.lua: in function 'notify'
.../remote-nvim.nvim/lua/remote-nvim/providers/provider.lua:802: in function <.../remote-nvim.nvim/lua/remote-nvim/providers/provider.lua:801>
Select Dev Containers: Launch current project in devcontainer
Follow steps and choose Launch local Neovim client?
Get the error
Expected behavior
Connect to my devcontainer.
Screenshot/Screencast(s)
System information
Your local OS: MacOS Sonoma 14.0
Local Neovim version: NVIM v0.10.0
Build type: Release
LuaJIT 2.1.1713484068
Remote host OS (if applicable): Linux db7593b9ebcf 6.9.6-orbstack-00147-gb0567c7c0069 feat(remote-nvim): Make SSH jobs async #1 SMP Sun Jun 23 23:24:08 UTC 2024 aarch64 GNU/Linux
Remote Neovim version (if applicable): 10.0, installed via remote-nvim,
Additional context
No
The text was updated successfully, but these errors were encountered:
Describe the bug
I tried to launch a devcontainer of https://github.com/moby/moby project and attach to it, but failed with error
To reproduce
Dev Containers: Launch current project in devcontainer
Launch local Neovim client?
Expected behavior
Connect to my devcontainer.
Screenshot/Screencast(s)
System information
Your local OS: MacOS Sonoma 14.0
Local Neovim version: NVIM v0.10.0
Build type: Release
LuaJIT 2.1.1713484068
Remote host OS (if applicable): Linux db7593b9ebcf 6.9.6-orbstack-00147-gb0567c7c0069 feat(remote-nvim): Make SSH jobs async #1 SMP Sun Jun 23 23:24:08 UTC 2024 aarch64 GNU/Linux
Remote Neovim version (if applicable): 10.0, installed via remote-nvim,
Additional context
No
The text was updated successfully, but these errors were encountered: