| Just noticed that I did a "Reply" rather than "Reply list" on my
      previous message. Nevermind. Anyway, I think I got to the bottom of the problem. The Readapt
      DAP apparently only supports communication over a network socket.
      And what I did not quite realise before digging into the LSP4E
      code is that when you use "setLaunchDebugAdapter", the
      communication is expected to happen over stdin/stdout. I've opened a feature request here:
      https://github.com/castwide/readapt/issues/3 Of course, one workaround would be to start the Readapt process
      from within my plugin and then use "setAttachDebugAdapter" to
      connect over a socket. However, that adds complexity and I would
      have to handle port numbers carefully, so I'll first wait and see
      what the author responds. Thanks, Pierre-Yves
 On 21/10/2019 19:17, Mickael Istria
      wrote:
 
      
      
        Hi Pierre-Yves, 
 IIRC, I often noticed those messages when passing erroneous
          argument to the CLI so the process was basically not answering
          what's expected. But anyway, I think this issue may be very specific from a
          LS to the other, so my answer doesn't mean much. If you find out a "standard" reason for this message, feel
          free to either improve code to avoid the error or improve the
          message and/or add a note about it somewhere in the
          documentation so it can be found later.
 HTH
 
 
        
        Hello
          all!
 I'm trying to add the Readapt debug adapter
 (https://github.com/castwide/readapt)
          to my Ruby LSP-based plugin
 (https://github.com/PyvesB/eclipse-solargraph).
 
 Unfortunately, I can't quite get things working correctly. I
          implemented
 a very simple debug launch shortcut and a DSPLaunchDelegate.
          When the
 debug shortcut is launched, I can see the Debug server
          starting up (a
 monitor console appears with "Readapt Debugger 0.7.1 is
          listening
 HOST=127.0.0.1 PORT=1234 PID=XXXXX"), but the
          DSPLaunchDelegate stays
 stuck at "Starting debug session: Initializing connection to
          debug adapter".
 
 Any ideas? I've shared my work in progress on a branch
 (https://github.com/PyvesB/eclipse-solargraph/tree/debug).
          If you have
 Ruby set up on your machine and want to try things out, run
          "gem install
 readapt" and simply replace the currently hardcoded location
          on
 ReadaptDebugRunDelegate:27.
 
 Note that I have successfully managed to make the reverse
          pattern work,
 i.e. starting Readapt from the command line and making the
 DSPLaunchDelegate attach to the exisitng server.
 
 Thanks in advance!
 
 Pierre-Yves
 
 
 
 
 
 _______________________________________________
 lsp4e-dev mailing list
 lsp4e-dev@xxxxxxxxxxx
 To change your delivery options, retrieve your password, or
          unsubscribe from this list, visit
 https://www.eclipse.org/mailman/listinfo/lsp4e-dev
 
 
 --
 
 
 _______________________________________________
lsp4e-dev mailing list
lsp4e-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/lsp4e-dev
 |