Closed vorburger closed 7 months ago
github-actions[bot]
commented
7 months ago 2 files ±0 2 suites ±0 5h 51m 9s :stopwatch: + 6m 57s 6 tests ±0 6 :white_check_mark: ±0 0 :zzz: ±0 0 :x: ±0 12 runs ±0 12 :white_check_mark: ±0 0 :zzz: ±0 0 :x: ±0
Results for commit c6c138b6. ± Comparison against base commit df47b0cb.
:recycle: This comment has been updated with latest results.
vorburger
commented
7 months ago Is there a way to increase logging verbosity which we could document here?
Where does it actually log when it launches Bazel do to the queries to configure the classpath? That's not in the .log and the client.log-2024* from JDT, right? I don't see anything about that there (even now that magically it works again for me).
I know the Terminal has 2 tabs for Bazel Build Status and Java Build Status - let me amend to add a note to look at that...
guw
commented
7 months ago @vorburger I noticed the missing logging too. I suspect something is not ok with JDTLS SLF4J & Logback setup. I am investigating. Probably worth moving this into a separate topic.
vorburger
commented
7 months ago @vorburger I noticed the missing logging too. I suspect something is not ok with JDTLS SLF4J & Logback setup. I am investigating. Probably worth moving this into a separate topic.
==> #100 (yay, 💯 🚀 )
I just had it "not work" again...
... and this is a bunch of things I tried.
No cleaning helped, and then I did an update of the extension (thus the uninstall/reinstall tip), and it worked again.
Which seems very weird, given that there don't seem to be any major changes recently.
The menus were there, the extension was "activated" according to VSC, but it just didn't configure the project.
@guw