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
{{ message }}
This repository has been archived by the owner on Apr 15, 2021. It is now read-only.
I use Dls within IntelliJ using LSP plugin. LSP notifies me in case Dls is crashing. Unfortunately the Dls log file does not contain any information about the crash. Actually the log does not even indicate that a crash occurred.
Could you check whether you could write exception stack trace to the log file?
The text was updated successfully, but these errors were encountered:
When DLS crashes, it's because of an Error, all Exceptions are handled as "internal errors".
So by default, I simply let DLS die a horrible death when it happens, since doing anything after an Error has been thrown is potentially unsafe.
Since #12, there is a catchErrors initialization option, that actually lets DLS catche errors too. I would tend to argue that it could be the role of the client to check the process' stderr when it crashes though.
I use Dls within IntelliJ using LSP plugin. LSP notifies me in case Dls is crashing. Unfortunately the Dls log file does not contain any information about the crash. Actually the log does not even indicate that a crash occurred.
Could you check whether you could write exception stack trace to the log file?
The text was updated successfully, but these errors were encountered: