jint_lzxy_

I think we're still missing some information (mainly a reliable repro / memory map) from the author.

We need more information to know what exactly happened: First clean lsp logs: ```shell truncate -c -s 0 ~/.local/state/nvim/lsp.log ``` Then add this line to the bottom of `lsp.lua` ```lua...

> Hmm that's right, I can see progress after enable other plugins. But how to distinguish whether it's because black and ruff are too fast or they don't support progress?...

To streamline the message: ```console .../lua/vim/lsp.lua:1428 "LSP[pylsp]" "initialize_params" { ... workDoneProgress = true ... }, ``` So ys `pylsp` _does_ support progress, but b/c `pylsp` doesn't need too much time...

> we don't use null-ls in python, ruff and black are integrated in pylsp as plugins Oh sorry about this - I forgot `ruff` and `black` have already been integrated...

@fecet is it gd to close this issue now?

> if adding orgmode would benefit most neovim users. If memory serves me correctly, I think this is exactly why we dropped orgmode around two years ago. It's undeniably powerful,...

> I'm not sure which upstream it relates to 😭 so I post it here It seems like this issue is indeed on our end. I also work with Swift...

> I tried the solution (TSUpdate && TSInstall! swift) and restart nvim, the issue is gone. Does this work for you? Yeah I find it super handy for like 99%...

### Check before merging Sometimes `nvim` crashes **during exit** (`:q`) _(SIGABRT)_, but it cannot be reliably reproduced. This would need to be tested on more platforms. However, this issue only...