rust-analyzer - no diagnostics on macOS

[ethanuppal]

Have you read the docs and searched existing issues?

• I have read the README's troubleshooting guide and FAQ(https://github.com/mrcjkb/rustaceanvim?tab=readme-ov-file#left_speech_bubble-faq).
• I am using the latest rustaceanvim release.
• I have searched existing issues.
• I have searched existing discussions.
• I have searched the existing issues of other plugins related to this issue (if applicable).
• I have searched the existing rust-analyzer issues (if applicable).
• I can reproduce the issue with stable Neovim (not a distribution or nightly) and the minimal config.
• This is an issue about rustaceanvim, not rust-analyzer or Neovim.
• This is not an issue with autocompletion.

Neovim version (nvim -v)

v0.10.4 and v0.11.0

Operating system/version

macOS 14.7

Output of :checkhealth rustaceanvim

==============================================================================
rustaceanvim:                           require("rustaceanvim.health").check()

Checking for Lua dependencies ~
- OK optional dependency nvim-dap not installed. Needed for debugging features [mfussenegger/nvim-dap](https://github.com/mfussenegger/nvim-dap)

Checking external dependencies ~
- OK rust-analyzer: found rust-analyzer 1.86.0 (05f9846f893 2025-03-31)
- OK Cargo: found cargo 1.86.0 (adf9b6ad1 2025-02-28)
- OK rustc: found rustc 1.86.0 (05f9846f8 2025-03-31)
- ERROR cargo-nextest: not found: Unsuported version. Required >=0.9.81, but found cargo-nextest 0.9.70

    rustaceanvim requires [cargo-nextest](https://nexte.st).
          Next generation test runner for Rust projects.
    Optional dependency, required if the 'tools.enable_nextest' option is set.
  
    

Checking config ~
- OK No errors found in config.

Checking for conflicting plugins ~
- OK No conflicting plugins detected.

Checking for tree-sitter parser ~
- OK tree-sitter parser for Rust detected.

How to reproduce the issue

1. Use the following version of `rust-analyzer`:


$ rust-analyzer --version
rust-analyzer 1.86.0 (05f9846f893 2025-03-31)


2. Use an undefined type.

Expected behaviour

Diagnostics should be created.

Actual behaviour

No diagnostics are created.

The minimal config used to reproduce this issue.

vim.env.LAZY_STDPATH = '.repro'
load(vim.fn.system('curl -s https://raw.githubusercontent.com/folke/lazy.nvim/main/bootstrap.lua'))()

require('lazy.minit').repro {
  spec = {
    {
      'mrcjkb/rustaceanvim',
      version = '^6',
      init = function()
        -- Configure rustaceanvim here
        vim.g.rustaceanvim = {}
      end,
      lazy = false,
    },
  },
}

[mrcjkb]

Hey 👋

This is very unlikely to be a rustaceanvim bug.
Sometimes rust-analyzer has issues on macOS (e.g. if the build wasn't code-signed, it gets blocked by SIP, without warnings or crashes).

[ethanuppal]

Maybe I should have clarified.

All other features of the LSP (symbols, hover, etc) work. It's just diagnostics that don't work...

[ethanuppal]

Related: rust-lang/rust-analyzer#19663

[mrcjkb]

That issue does not seem related.

[ethanuppal]

To clarify --- it is related because I am also seeing that error in my :LspLog, although other aspects of the LSP still function (such as hover), so it is not entirely the same issue.

[mrcjkb]

rust-lang/rust-analyzer#19743 (comment)