Ólafur Páll Geirsson
Ólafur Páll Geirsson
Also, have you tried the `--watch` flag? You always pay a base overhead from initializing the compiler if you run `mdoc/run` on every iterations. With `--watch` you get the fastest...
Thank you for reporting! I can see how this would be useful. This feature is unrelated to #245, that PR is about managing the life-cycle of custom modifiers. I think...
Thank you for reporting! I'm not aware of any efforts or solutions to integrate mdoc with asciidoc. Internally, mdoc isn't *easily* extendable to other syntaxes but I think it's possible...
Feel free to close this issue if you can't reproduce. I've hit on it several times today and figured it might as well be worth reporting in case other people...
I'll report back if I can reproduce. Most likely it's an uncaught exception from the command handler in VS Code and the modal message is reported by the editor.
I hit on this issue again and can reliably reproduce in my local session. It was even able to reproduce once after a "Reload Window". Here's [lsp.trace.json.zip](https://github.com/scalameta/metals/files/7357165/lsp.trace.json.zip). I had compile...
@dos65 I don't think that stack trace is related to the cascade compile failure, but maybe it is 🤷
I'm seeing the same error with other commands like "Connect to build server" We can transfer this issue to the VS Code extension since there's nothing wrong about the Metals...
Do we have logs for this error? Metals always “retries” by nature of calling coursier on every server start. I’m not sure we should retry on the metals side
@soronpo are you behind a VPN?