Error processing message !

[akarsh1995]

Steps to reproduce:

from torch.optim.adam import Adam

Adam() # when lsp tries to give arguments hint in the mini buffer. The following error is invoked.

Error processing message (error "Failed to handle #s(hash-table size 65 test equal rehash-size 1.5 rehash-threshold 0.8125 data (kind plaintext))"). [5 times]

Most likely the error seems to be within emacs bounds.

[seagle0128]

I think it's an issue of lsp-mode core. @yyoncho can u pls take a look?

[yyoncho]

@akarsh1995 can you make sure that you are using latest version of all lsp-mode related packages? I think this is lsp-ui issue fixed long time ago.

[akarsh1995]

@yyoncho

@akarsh1995 can you make sure that you are using latest version of all lsp-mode related packages? I think this is lsp-ui issue fixed long time ago.

Emacs Version

GNU Emacs 26.3 (build 1, x86_64-apple-darwin19.6.0, NS appkit-1894.60 Version 10.15.6 (Build 19G73))
 of 2020-08-05

Relevant packages info

    Package: lsp-mode
     Source: Straight
     Pinned: 0131f1f4c9e7823955c3b1f80881fcd7c2eaa551
      Build: grafted, HEAD 0131f1f 2020-07-28 18:17:55 +0300
             (:type git :flavor melpa :host github :repo "emacs-lsp/lsp-mode" :package "lsp-mode" :local-repo "lsp-mode")
   Homepage: https://github.com/emacs-lsp/lsp-mode
    Modules: Declared by the following Doom modules:
             :tools lsp
    Configs: This package is configured in the following locations:
             modules/lang/lua/config.el:42:      (after! lsp-mode
             modules/tools/lsp/+lsp.el:11:(use-package! lsp-mode


    Package: lsp-python-ms
     Source: Straight
     Pinned: d42ffc2cc27ce36b5a7646ea922441f4c93b2678
      Build: grafted, HEAD d42ffc2 2020-07-25 15:58:02 +0800
             (:type git :flavor melpa :host github :repo "emacs-lsp/lsp-python-ms" :package "lsp-python-ms" :local-repo "lsp-python-ms")
   Homepage: https://github.com/emacs-lsp/lsp-python-ms
    Modules: Declared by the following Doom modules:
             :lang python
    Configs: This package is configured in the following locations:
             modules/lang/python/config.el:317:  (use-package! lsp-python-ms


    Package: lsp-ui
     Source: Straight
     Pinned: 1f3e9700395f4fae024ca45ca64c8d70e99b39d2
      Build: grafted, HEAD 1f3e970 2020-07-18 12:35:32 +0200
             (:type git :flavor melpa :files
                    (:defaults "lsp-ui-doc.html" "lsp-ui-pkg.el")
                    :host github :repo "emacs-lsp/lsp-ui" :package "lsp-ui" :local-repo "lsp-ui")
   Homepage: https://github.com/emacs-lsp/lsp-ui
    Modules: Declared by the following Doom modules:
             :tools lsp
    Configs: This package is configured in the following locations:
             modules/tools/lsp/+lsp.el:165:(use-package! lsp-ui

lsp diagnose output:

Checking for Native JSON support: ERROR
Checking emacs version has `read-process-output-max': ERROR
Using company-capf: OK
Check emacs supports `read-process-output-max': ERROR
Check `read-process-output-max' default has been changed from 4k: ERROR
Byte compiled against Native JSON (recompile lsp-mode if failing when Native JSON available): ERROR
`gc-cons-threshold' increased?: OK

[yyoncho]

I tested with lsp-start-plain.el (as described in lsp-mode bug template) and it works fine with the provided snippet.

[orlandini]

any news on that? I'm facing some similar right now. I've deleted everything in my ~/.emacs.d/elpa directory so I would assume I am using the most recent version from packages.

lsp diagnose output

Checking for Native JSON support: OK
Check emacs supports `read-process-output-max': OK
Check `read-process-output-max' default has been changed from 4k: OK
Byte compiled against Native JSON (recompile lsp-mode if failing when Native JSON available): OK
`gc-cons-threshold' increased?: OK
Using gccemacs with emacs lisp native compilation (https://akrl.sdf.org/gccemacs.html): NOT AVAILABLE (OPTIONAL)

[UniverseFly]

Have the same issue, expecting some updates

[ItsNilDev]

I'm experiencing this issue too

[offendo]

Same issue, any updates?

[nchodosh]

Also having this issue

[ameamenoame]

fix plz