Kobayashi

Are there any update on this?

In case someone else find this issue, another workaround without forking anything would be applying a patch to openssh, like this: ```nix # In configuration.nix nixpkgs.overlays = [ (final: prev:...

VSCode already supports custom folding ranges in its latest version: https://code.visualstudio.com/updates/v1_70#_fold-selection. Maybe it's okay to close this issue?

@barendventer Looks like I misunderstood it. Here is a workaround I found later: https://marketplace.visualstudio.com/items?itemName=zokugun.explicit-folding

I'm receiving a lot of logs like this if `--verbose` is enabled in `ghcide-tests`. And finally got OOM even with 64GB memory. So disabling it for now

I see. In `lsp`, there is a debug log, printing response body: https://github.com/haskell/lsp/blob/8b63438313828a31ba1065ea865e504d532d093e/lsp/src/Language/LSP/Server/Control.hs#L224-L234 And in HLS, our logger sends a copy of log to LSP client: https://github.com/haskell/haskell-language-server/blob/347a7187f20242540926b9927c59a45b18798c67/exe/Main.hs#L72-L82 Then it goes...

> It's nice to be able to log the responses from LSP And some other tests depend on the logs, I had to fix them one by one. This makes...

Finally, the CI is almost green.

VSCode already supports custom folding ranges in its latest version: https://code.visualstudio.com/updates/v1_70#_fold-selection. [LSP folding range](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_foldingRange) is another thing. It allows us to provide Haskell-specific folding ranges instead of the default ones...

In conclusion, we have nothing to do about custom folding ranges, as Language Server Protocol doesn't support it. I recommend converting the purpose of this issue to merging language pragmas...