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

Connection not established due to invalid slot name #95

Closed
theSuess opened this issue Mar 26, 2024 · 5 comments
Closed

Connection not established due to invalid slot name #95

theSuess opened this issue Mar 26, 2024 · 5 comments

Comments

@theSuess
Copy link

I'm trying to use dape with delve to debug a go program but it seems like the connection cannot be established due to a missing slot.

Dape sets up all windows and starts dlv succesfully but after that I only get the following message:

slot-missing: Invalid slot name #<dape-connection dape-connection-31417dc>, :events-buffer-config

Enabling debug information does not create the *dape-connection events* buffer and no additional information is shown in the repl.

I'm using the latest elpa version of dape with emacs 29.2

@svaante
Copy link
Owner

svaante commented Mar 26, 2024

Hi,
How do you install dape? Because you are not getting the latest version of jsonrpc.el. Which package.el should download and install for you.

M-x package-install

@theSuess
Copy link
Author

I'm using straight.el as my package manager in combination with use-package.
My configuration is literally just:

(use-package dape)

@svaante
Copy link
Owner

svaante commented Mar 26, 2024

With M-x list-packages is the following row present?

  jsonrpc                        1.0.25         dependency            JSON-RPC library

Otherwise M-x package-refresh-contents might do the thing together with package-upgrade jsonrpc.
I still don't understand the inner workings with package.el and package loading order.

@theSuess
Copy link
Author

It's using the built-in jsonrpc for me. Judging from #70, using a newer jsonrpc version should fix my issue. I'll see if I can get this working

@theSuess
Copy link
Author

Yes, updating jsonrpc fixed the issue - thanks for pointing out the incompatibility

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants