Cannot connect to neopyter extension #15

Activity

1. AbaoFromCUG commented on Oct 11, 2024

   

   AbaoFromCUG

   on Oct 11, 2024

   Collaborator

   More actions

   Looks weird, Whenever you open a xxx.ju.py (e.g. :e main.ju.py), the neovim plugin(neopyter) should be activated, it should look like:

   neopyter: version ~
   - neovim plugin(neopyter@0.2.6) status: active
   - jupyter lab extension: don't connect
   
   neopyter: status ~
   - attach=ready, connect=syncing
     
   -   file                           attach     connect    remote_path
   - * main.ju.py                     true       false
   
   

   and here is my all :checkhealth neopyter result

   
   ==============================================================================
   neopyter: require("neopyter.health").check()
   
   neopyter: config ~
   - {
       auto_attach = true,
       auto_connect = true,
       file_pattern = { "*.ju.*" },
       filename_mapper = <function 1>,
       highlight = {
         enable = true,
         shortsighted = false
       },
       jupyter = {
         auto_activate_file = true,
         scroll = {
           align = "auto",
           enable = true
         }
       },
       mode = "direct",
       on_attach = <function 2>,
       parser = {
         line_magic = true,
         trim_whitespace = true
       },
       remote_address = "127.0.0.1:9001",
       textobject = {
         enable = true
       },
       use_default_keybindings = true
     }
   
   neopyter: version ~
   - neovim plugin(neopyter@0.2.6) status: active
   - jupyter lab extension: don't connect
   
   neopyter: status ~
   - attach=ready, connect=syncing
     
   -   file                           attach     connect    remote_path
   - * main.ju.py                     true       false
   

   In the current state, neovim should listen to the network port 9001

   lsof -i:9001
   COMMAND   PID USER FD   TYPE DEVICE SIZE/OFF NODE NAME
   nvim    21975 abao 31u  IPv4  66442      0t0  TCP localhost:etlservicemgr (LISTEN)
   

   Some tips may help you

   • Don't open two neovim program instance with same address be listened
   • Neopyter(neovim plugin) is activated by an autocmd of BufReadPost with file_pattern automatically
2. vanducng commented on Oct 11, 2024

   

   vanducng

   on Oct 11, 2024

   Author

   More actions

   Thanks @AbaoFromCUG,
   I think there was an issue with the socket connection. I got it fixed by following this discussion: zauberzeug/nicegui#1178 (comment)

   

   I now can see it listened to port 9001 but status is still inactive. I will try to debug more.

   
3. AbaoFromCUG

   closed this as completedon Jan 11, 2025
4. eokoshi commented on Jun 22, 2026

   

   eokoshi

   on Jun 22, 2026

   More actions

   what is the solution?
5. AbaoFromCUG commented on Jun 26, 2026

   

   AbaoFromCUG

   on Jun 26, 2026

   Collaborator

   More actions

   what is the solution?

   As mentioned:

   Looks like editing /etc/hosts to explicitly use the hostname vs. localhost is a workaround. Just not ideal from a DX perspective.

   127.0.0.1       localhost
   127.0.0.1       mbp
   255.255.255.255 broadcasthost
   ::1             localhost
   

   Could you share your :checkhealth neopyter?