Plugin reliably fails with nvim 0.11.X

[savchenko]

I have spent a good hour trying to get either direct or proxy up and running, but to no avail.

My setup is rather minimalistic, so I am not certain where the incompatibility is exactly.

I see plenty of various errors, e.g.

Error executing vim.schedule lua callback: ...share/nvim/lazy/plenary.nvim/lua/plenary/async/async.lua:18: The coroutine failed with this message: ...are/nvim/lazy/neopyter
/lua/neopyter/jupyter/notebook.lua:236: bad argument #1 to 'ipairs' (table expected, got nil)                                                                               
stack traceback:                                                                                                                                                            
        [C]: in function 'error'                                                                                                                                            
        ...share/nvim/lazy/plenary.nvim/lua/plenary/async/async.lua:18: in function 'callback_or_next'                                                                      
        ...share/nvim/lazy/plenary.nvim/lua/plenary/async/async.lua:45: in function <...share/nvim/lazy/plenary.nvim/lua/plenary/async/async.lua:44> 

Or, just after opening the *.ju file:

Error detected while processing BufReadPost Autocommands for "*.ju.*"..BufWinEnter Autocommands for "*.ju.*":
Error executing lua callback: ...share/nvim/lazy/plenary.nvim/lua/plenary/async/async.lua:18: The coroutine failed with this message: ...are/nvim/lazy/neopyter/lua/neopyter
/jupyter/notebook.lua:153: attempt to index a nil value
stack traceback:
        [C]: in function 'error'
        ...share/nvim/lazy/plenary.nvim/lua/plenary/async/async.lua:18: in function 'callback_or_next'
        ...share/nvim/lazy/plenary.nvim/lua/plenary/async/async.lua:45: in function 'step'
        ...share/nvim/lazy/plenary.nvim/lua/plenary/async/async.lua:48: in function 'execute'
        ...share/nvim/lazy/plenary.nvim/lua/plenary/async/async.lua:108: in function 'run'
        ...r/.local/share/nvim/lazy/neopyter/lua/neopyter/async.lua:52: in function <...r/.local/share/nvim/lazy/neopyter/lua/neopyter/async.lua:50>
        [C]: in function 'resume'
        ...share/nvim/lazy/plenary.nvim/lua/plenary/async/async.lua:45: in function 'step'
        ...share/nvim/lazy/plenary.nvim/lua/plenary/async/async.lua:48: in function 'execute'
        ...share/nvim/lazy/plenary.nvim/lua/plenary/async/async.lua:108: in function 'run'
        ...r/.local/share/nvim/lazy/neopyter/lua/neopyter/async.lua:52: in function <...r/.local/share/nvim/lazy/neopyter/lua/neopyter/async.lua:50>

I think adding <h1> warning to the README.md will save everyone time if the extension is indeed incompatible with latest stable NeoVim and/or Jupyter Lab.

NVIM v0.11.7
Jupyter Lab Version 4.5.5

Ping @AbaoFromCUG

[AbaoFromCUG]

Hi, do you install a treesitter parser of python? Cloud your share your :checkhealth neopyter. e.g.

neopyter:                                                                   ✅

neopyter: config ~
- {
    auto_attach = true,
    auto_connect = true,
    file_pattern = { "*.ju.*" },
    filename_mapper = <function 1>,
    highlight = {
      enable = true,
      mode = "separator"
    },
    injection = {
      enable = true
    },
    jupyter = {
      auto_activate_file = true,
      partial_sync = false,
      scroll = {
        align = "auto",
        enable = true
      }
    },
    mode = "direct",
    on_attach = <function 2>,
    parser = {
      python = {},
      r = {},
      trim_whitespace = true
    },
    remote_address = "127.0.0.1:9001",
    textobject = {
      enable = true,
      queries = { "cellseparator", "cellcontent", "cell" }
    }
  }

neopyter: treesitter ~
- ✅ OK parser: python parser is installed
- ✅ OK parser: r parser is installed
- ✅ OK parser: markdown parser is installed

neopyter: version ~
- os platform of neovim: Linux
- neovim version: 0.11.7+gcd90ec7cdc
- neovim plugin(neopyter@0.4.0) status: active
- jupyter lab extension(neopyter@0.4.0): active

neopyter: status ~
- attach: tracking with neopyter
  connect: synchronizing with jupyter lab

- file                           attach     connect    remote_path
  * doc/specification.ju.py        true       true       doc/specification.ipynb

[AbaoFromCUG]

@savchenko By the way, the latest stable neovim is v0.12.*.

[savchenko]

Yes, I do. I have observed errors in both proxy and direct modes.

After throwing a dice (e.g. restarting both nvim and jupyter lab several times), this is the best I've got:

neopyter: config  
- {
    auto_attach = true,
    auto_connect = true,
    file_pattern = { "*.ju.*" },
    filename_mapper = <function 1>,
    highlight = {
      enable = true,
      mode = "separator"
    },
    injection = {
      enable = true
    },
    jupyter = {
      auto_activate_file = true,
      partial_sync = false,
      scroll = {
        align = "center",
        enable = true
      }
    },
    mode = "direct",
    on_attach = <function 2>,
    parser = {
      python = {},
      r = {},
      trim_whitespace = false
    },
    remote_address = "127.0.0.1:9001",
    textobject = {
      enable = true,
      queries = { "cellseparator", "cellcontent", "cell" }
    }
  }

neopyter: treesitter  
- ✅ OK parser: python parser is installed
- ✅ OK parser: r parser is installed
- ✅ OK parser: markdown parser is installed

neopyter: version  
- os platform of neovim: Linux
- neovim version: 0.11.7+gcd90ec7cdc
- neovim plugin(neopyter@0.4.0) status: active
- jupyter lab extension(neopyter@0.4.0): active

neopyter: status  
- attach: tracking with neopyter
  connect: synchronizing with jupyter lab

- file                           attach     connect    remote_path
  * notebook.ju.py              true       false

Still, it wasn't reliable with odd cryptic error thrown into :messages.

You are correct that 0.12 is now stable, is this plugin compatible with 0.11 though? 0.12 was released 3 weeks ago.

[AbaoFromCUG]

For this issue, thanks for your feedback, I already dev a solution in #55

Cause: If you setup tree-sitter's parser after neopyter, neopyter will failed to load parser.

My solution is to delay load/check parser when attaching buf

---

For v0.11, which will be supported in separated branch named v0.11-compat , because I would like to use vim._async (which is introduced in v0.12.*) to replace plenary.async.
See more details in #54

A v0.11-compat branch and test in #56

[AbaoFromCUG]

I already created a branch named v0.11-compat, https://github.com/SUSTech-data/neopyter/tree/v0.11-compat

This branch will depend to plenary.nvim

Feel free to use

        {
            "SUSTech-data/neopyter",
            priority = 1000,
            lazy = false,
            branch="v0.11-compat",  -- the branch
            dependencies = {
                "nvim-lua/plenary.nvim",
                "AbaoFromCUG/websocket.nvim", -- for mode='direct'
            },
            ---@type neopyter.Option
            opts = {
                mode = "direct",
                remote_address = "127.0.0.1:9001",
                file_pattern = { "*.ju.*" },
                on_attach = function(bufnr)
                    -- do some buffer keymap
                end,
            },
        },

Or give me more feedback via

We provide minimize reproduction example in ./example:

• In one terminal, start jupyter lab

cd example
uv run jupyter lab --ip=0.0.0.0 --port=7088

In another terminal, start neovim

cd example
nvim -u repro.lua main.ju.py