LSP :: Connected to [clojure-lsp:10583]. [2 times]
Error in post-command-hook (lsp-ui-sideline): (invalid-function lsp-ui--with-no-redisplay)
Error while checking syntax automatically: (invalid-function lsp-ui--with-no-redisplay)
Error running timer: (invalid-function lsp-ui--with-no-redisplay)
Error running timer 'lsp--on-idle': (invalid-function lsp-ui--with-no-redisplay) [5 times]
..
lsp-ui-peek--render: Invalid function: lsp-ui--mute-apply [2 times]
Error processing message (invalid-function lsp-ui--with-no-redisplay).
lsp-ui--workspace-path: Wrong type argument: arrayp, nil [2 times]

actually, I guess this is an issue with lsp-ui and not clojure-lsp, sorry 🙂

https://github.com/emacs-lsp/lsp-ui/issues/675

The lsp-ui PR was already reverted

Check clojure-lsp log, it's probably a configuration issue with your project, not related with latest release

https://clojure-lsp.io/troubleshooting/

also try rm -rf .lsp/.cache

and reload vcode window

i’ll try deleting the cache and restarting. it’s strange that only the orchard repo is having problems, everything else works fine

it could be some project issue so, checking the logs is the best way to find

i tried via console and that doesn’t produce a log file in that project the calva included start produces:

2022-01-03T18:56:06.582Z  ERROR [taoensso.timbre:796] - Uncaught exception on thread: main
 [37mclojure_lsp.main.main[m  [32m             [m
                   [37m...[m  [32m             [m
[33mclojure-lsp.main/[1;33m-main[m  [32mmain.clj: 169[m
[33mclojure-lsp.main/[1;33m-main[m  [32mmain.clj: 171[m
 [33mclojure-lsp.main/[1;33mexit[m  [32mmain.clj: 124[m
                   [37m...[m  [32m             [m
[1;31mjava.lang.NullPointerException[m: [3m[m

2022-01-03T18:56:06.853Z  INFO [clojure-lsp.server:310] - Parent process 44260 is not running - exiting server
2022-01-03T18:56:06.856Z  INFO [clojure-lsp.server:409] - Exitting...

btw orchard does include some strange corner cases in the code for testing purposes, so it might be a problem with that

let me try download orchard and test it

clojure-lsp works pretty well to me on this project with emacs, let me try calva

on calva there is something that it blocks clojure-lsp for some reason indeed

that's really odd, I can't find why only happens this on calva

is it working on the command line for you? mine keeps running but writes no log file

yeah, it does work on terminal for me:

I think I found something, one sec

i was running it as a server, diagnostics works for me as well if i can help fix the calva issue let me know. i just realized how anoying it is to run without lsp:)

Found the issue

for some reason, clj-kondo outputs for orchard project

..................

and this crashes vscode communication with clojure-lsp for some reason, which makes sense as it's not allowed those chars, only json

2 questions there: • clojure-lsp should handle stdout output from kondo which I will fix it • why clj-kondo prints this dots only for some projects? maybe @U04V15CAJ can help help understand this

It looks sounds kind of loading from clj-kondo side, but I never saw that on other projects or didn't noticed it:

This is probably because of {:output {:progress true}}

hum, orchard does have this config

https://github.com/clojure-emacs/orchard/blob/aa6af7b90cedc28c3cb3bdf1d146f1179f37dca4/.clj-kondo/config.edn#L1

makes sense now

clojure-lsp should probably catch clj-kondo output and log to the file instead of stdout so

@UKFSJSM38 Do you add an additional config in lsp? You can override this by always setting it to false

yeah, we can override this or just log to file instead of stdout which makes sense to me

as clj-kondo can print other things in the future and may cause issues like that

but clj-kondo should have printed this to stderr btw https://github.com/clj-kondo/clj-kondo/blob/51b10ac887f5b0deb28b3b8f749e1590ffa24458/src/clj_kondo/impl/analyzer.clj#L2487 I made this feature a long time ago and I didn't think anyone used it

haha, probably we should fix clj-kondo as well so

PR welcome to fix it or I'll fix it soon

no hurries, I already made the commit on clojure-lsp to catch stdout prints as well

thanks for the help

thanks

@U02EMBDU2JU fixed on clojure-lsp master

I think I'll do another patch release just to fix that

big thanks to both of you, the support time is unreal :)

https://github.com/clj-kondo/clj-kondo/issues/1523