Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Recently started getting cannot resume dead coroutine errors #5

Open
megalithic opened this issue May 30, 2024 · 1 comment
Open

Recently started getting cannot resume dead coroutine errors #5

megalithic opened this issue May 30, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@megalithic
Copy link
Contributor

This seems to only happen if I've opened the output-panel on a long-running nvim session. If I've not opened the output-panel at all in that long-running nvim session, it never hits this.

My plugin setup:

  {
    "mhanberg/output-panel.nvim",
    event = "VeryLazy",
    keys = {
      {
        "<leader>lip",
        ":OutputPanel<CR>",
        desc = "lsp: open output panel",
      },
    },
    cmd = { "OutputPanel" },
    opts = true,
  },

REF:

local tab = create_tab(client.name)

ERROR:

Error executing vim.schedule lua callback: ...re/nvim/lazy/output-panel.nvim/lua/output_panel/init.lua:84: cannot resume dead coroutine
stack traceback:
        [C]: in function 'create_tab'
        ...re/nvim/lazy/output-panel.nvim/lua/output_panel/init.lua:84: in function 'handler'
        /usr/local/share/nvim/runtime/lua/vim/lsp/client.lua:1008: in function ''
        vim/_editor.lua: in function <vim/_editor.lua:0>
@mhanberg mhanberg added the bug Something isn't working label May 30, 2024
@megalithic
Copy link
Contributor Author

Planning to work on this, but will have to be a bit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants