Kirill Bulatov

https://github.com/zed-industries/zed/pull/8356 propagates whatever rust-analyzer sends us back in `experimental/serverStatus` notification, now we get `Failed to load workspace` mainly and potentially some other errors as pop-ups.

You're looking for https://github.com/zed-industries/zed/blob/e5d971f4c71aa2bb3c3aaea9d0838502c194992c/crates/editor/src/hover_popover.rs file, there are multiple flavors of those with their own `render` method responsible for drawing the thing.

VSCode: RustRover: It looks like we can add some padding, customize the border a bit, and maybe add more contrast? Not sure we need to get into anything fancy as...

This is now available in [v0.130.0-pre](https://zed.dev/releases/preview/0.130.0). 

Leak could be caused by the same issue as https://github.com/zed-industries/zed/issues/7438 More contribution to the memory bloat might be caused by the way we store LSP logs: they are capped but...

See also - https://github.com/zed-industries/zed/pull/7601

This is not about Zed but rather about r-a: https://github.com/rust-lang/rust-analyzer/issues/15554

Sorry, apparently things have changed and I did not pay attention — we have to double check that, but I still suspect it might bail down to a rust-analyzer issue.

Thank you for trying. I've observed something similar with `npm i` the other month, so it might be some issue with Zed FS watched indeed, so let's keep that open...

Log file initialization happens here: https://github.com/zed-industries/zed/blob/991c9ec441711a4c0b10ce595f3025f430123800/crates/zed/src/main.rs#L512-L534 We could output the whole thing into stdout, same as the `if stdout_is_a_pty()` branch above does. Also, there's `OpenLog` action that has to be...