Open jesperes opened 1 year ago
Since updating to lsp-ui version 20220823.1626, I'm starting to get errors like this now and then. I am guessing this related to lsp-ui, mostly because of the stacktrace:
20220823.1626
lsp-ui
Debugger entered--Lisp error: (wrong-type-argument listp default) lsp-ui-sideline--compute-height() #f(compiled-function (action) #<bytecode 0x15fae59>)(#<hash-table equal 3/65 0x1c39a11>) mapc(#f(compiled-function (action) #<bytecode 0x15fae59>) (#<hash-table equal 3/65 0x1c39a11>)) seq-do(#f(compiled-function (action) #<bytecode 0x15fae59>) (#<hash-table equal 3/65 0x1c39a11>)) lsp-ui-sideline--code-actions((#<hash-table equal 3/65 0x1c39a11>) 912 912) #f(compiled-function (actions) #<bytecode 0x1284509>)((#<hash-table equal 3/65 0x1c39a11>)) apply(#f(compiled-function (actions) #<bytecode 0x1284509>) (#<hash-table equal 3/65 0x1c39a11>)) #f(compiled-function (&rest args) #<bytecode 0x12a8d35>)((#<hash-table equal 3/65 0x1c39a11>)) #f(compiled-function (result) #<bytecode 0x131d009>)([#<hash-table equal 3/65 0x1c39a11>]) #f(compiled-function (result) #<bytecode 0x1331e15>)([#<hash-table equal 3/65 0x1c39a11>]) lsp--parser-on-message(#<hash-table equal 3/65 0x1c398e9> #s(lsp--workspace :ewoc nil :server-capabilities #<hash-table equal 17/65 0x2417d4d> :registered-server-capabilities nil :root "/home/jespereskilson/dev/kred" :client #s(lsp--client :language-id nil :add-on? nil :new-connection (:connect #f(compiled-function (filter sentinel name environment-fn) #<bytecode 0x21c6f65>) :test\? #f(compiled-function () #<bytecode 0x21c6f7d>)) :ignore-regexps nil :ignore-messages nil :notification-handlers #<hash-table equal 0/65 0x21c6f89> :request-handlers #<hash-table equal 0/65 0x21c71b9> :response-handlers #<hash-table eql 0/65 0x21c71d9> :prefix-function nil :uri-handlers #<hash-table equal 0/65 0x21c7831> :action-handlers #<hash-table equal 0/65 0x21c7b29> :major-modes (erlang-mode) :activation-fn nil :priority -1 :server-id erlang-ls :multi-root nil :initialization-options nil :semantic-tokens-faces-overrides nil :custom-capabilities nil :library-folders-fn nil :before-file-open-fn nil :initialized-fn nil :remote? nil :completion-in-comments? nil :path->uri-fn nil :uri->path-fn nil :environment-fn nil :after-open-fn nil :async-request-handlers #<hash-table equal 0/65 0x21c7d59> :download-server-fn nil :download-in-progress? nil :buffers nil :synchronize-sections nil) :host-root nil :proc #<process erlang-ls> :cmd-proc #<process erlang-ls> :buffers (#<buffer KRED-13226-kcore-upgrade-yaws-ec_UP.erl>) :semantic-tokens-faces nil :semantic-tokens-modifier-faces nil :extra-client-capabilities nil :status initialized :metadata #<hash-table equal 0/65 0x2376871> :watches #<hash-table equal 0/65 0x2376999> :workspace-folders nil :last-id 0 :status-string nil :shutdown-action nil :diagnostics #<hash-table equal 1/65 0x23769b9> :work-done-tokens #<hash-table equal 1/65 0x23ca0ad>)) #f(compiled-function (msg) #<bytecode 0x1c39a51>)(#<hash-table equal 3/65 0x1c398e9>) mapc(#f(compiled-function (msg) #<bytecode 0x1c39a51>) (#<hash-table equal 3/65 0x1c398e9>)) #f(compiled-function (proc input) #<bytecode 0x23ca0cd>)(#<process erlang-ls> "Content-Length: 312\015\n\015\n{\"id\":14,\"jsonrpc\":\"2.0\",\"result\":[{\"edit\":{\"changes\":{\"file:///home/jespereskilson/dev/kred/lib/upgrade/src/KRED-13226-kcore-upgrade-yaws-ec_UP.erl\":[{\"newText\":\"_SysNodes\",\"range\":{\"end\":{\"character\":45,\"line\":31},\"start\":{\"character\":37,\"line\":31}}}]}},\"kind\":\"quickfix\",\"title\":\"Did you mean '_SysNodes'?\"}]}")
Relevant versions involved: Emacs: 26.3 lsp-ui: 20220823.1626 LSP server: erlang_ls 0.9.0-539-g55a3854
This is my first bugreport here, so please let me know if you need any additional information.
Since updating to lsp-ui version
20220823.1626
, I'm starting to get errors like this now and then. I am guessing this related tolsp-ui
, mostly because of the stacktrace:Relevant versions involved: Emacs: 26.3 lsp-ui: 20220823.1626 LSP server: erlang_ls 0.9.0-539-g55a3854
This is my first bugreport here, so please let me know if you need any additional information.