Description

The Language Server Protocol (LSP) stops working as soon as I start typing in Neovim. The issue seems to be related to texlab as indicated by the error messages in the log file.

Environment

• Neovim version: v0.10.0
• Operating System: Linux 6.9.5-arch1-1
• Texlab version: v5.17.0

Error Logs

Here are the relevant logs when the issue occurs:

[START][2024-06-27 08:15:19] LSP logging initiated
[ERROR][2024-06-27 08:15:19] .../vim/lsp/rpc.lua:770 "rpc" "/home/fcb/.local/share/nvim/mason/bin/texlab" "stderr" "thread 'main' panicked at crates/parser/src/bibtex.rs:255:43:\ncalled `Result::unwrap()` on an `Err` value: ()\nnote: run with `RUST_BACKTRACE=1` environment variable to display a backtrace\n"
[ERROR][2024-06-27 08:15:19] .../vim/lsp/rpc.lua:770 "rpc" "/home/fcb/.local/share/nvim/mason/bin/texlab" "stderr" "thread '<unnamed>' panicked at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/lsp-server-0.7.6/src/stdio.rs:28:37:\nreceiver was dropped, failed to send a message: \"SendError(..)\"\n"

Additional Information

• The issue seems to be caused by an unwrap() call on an Err value in the BibTeX parser (crates/parser/src/bibtex.rs:255:43).

• Another error message indicates a dropped receiver failing to send a message in lsp-server (lsp-server-0.7.6/src/stdio.rs:28:37).

Possible Solution

Investigate the cause of the Err value in the BibTeX parser and handle the error appropriately to avoid the panic.

Thank you for looking into this issue!