You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Emacs modeline shows the startup status of clojure-lsp when starting. However, it gets stuck on Fetching libs for completions. See logs below.
Not fatal, as otherwise the LSP session seems to work fine. Not sure what that "fetching libs" functionality is, so something might break if it doesn't finish ok.
This is a async non blocking task that fetch libs for completion at project.clj/deps.edn, so you can completion lib names and versions, but it's supposed to be fast, but it seems a exception is happening, I'll fix it
Thanks, the fechting (sic) works fine now with the latest nightly ;)
2025-02-01T08:31:57.541Z INFO [clojure-lsp.db:79] - [DB] Reading transit analysis cache from /Users/lassemaatta/.cache/clojure-lsp/db.transit.json db took 956ms
2025-02-01T08:31:57.542Z INFO [clojure-lsp.feature.java-interop:271] - [Java] JDK source already present on global LSP cache dir.
2025-02-01T08:31:57.549Z INFO [clojure-lsp.dep-graph:280] - :maintain-dep-graph 5ms
2025-02-01T08:31:57.551Z INFO [clojure-lsp.feature.java-interop:312] - [Java] JDK source analysis cache loaded successfully.
2025-02-01T08:32:03.641Z INFO [clojure-lsp.feature.completion-lib:162] - Fechting all jar libs took 10584ms
2025-02-01T08:32:03.644Z INFO [clojure-lsp.handlers:197] - :did-open 10749ms
2025-02-01T08:32:03.644Z INFO [clojure-lsp.server:164] - :refreshing-test-tree 0ms
Describe the bug
Emacs modeline shows the startup status of
clojure-lsp
when starting. However, it gets stuck onFetching libs for completions
. See logs below.Not fatal, as otherwise the LSP session seems to work fine. Not sure what that "fetching libs" functionality is, so something might break if it doesn't finish ok.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Fetching libs doesn't crash.
Screenshots
Log - clojure-lsp
User details (please complete the following information):
The text was updated successfully, but these errors were encountered: