Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash possibly related to neotest when using it with Rust inside a workspace #372

Open
robamu opened this issue Feb 28, 2024 · 2 comments
Open
Assignees

Comments

@robamu
Copy link

robamu commented Feb 28, 2024

See the issue I posted in neotest-rust . I am not fully sure whether this is a neotest-rust problem or a general neotest problem, but others have had this issue as well.

If I open neovim inside a Rust workspace folder, everything works as expected. However, when I open neovim in a subfolder of that workspace and try to run tests or open the test tree with neotest, neovim crashes. Is this a known issue? I have had trouble to trace this to a single function, I tried reading the crash dumps of neovim, but it does not contain any useful information.

This only occurs on Ubuntu and not on MacOS which makes this issue even more weird.

The error can be reproduced by installing neotest and neotest-rust, opening neovim inside https://github.com/rouge8/neotest-rust/tree/main/tests/data/workspace/with_integration_tests and then either running any test inside that folder or simply opening the summary window. When opening neovim inside the workspace root itself, everything works without any issues.

@robamu robamu changed the title Possible crash when using neotest with Rust inside a workspace Crash possibly related to neotest when using it with Rust inside a workspace Feb 28, 2024
@duncanam
Copy link

For LunarVim users, add:

lvim.builtin.project.active = false
lvim.builtin.project.manual_mode = true

then navigate to the directory where your project is and lvim . to start there.

@jonathancyu
Copy link

I am also running into this issue, however I'm not using lunarvim. Is there another workaround here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants