You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
rustaceanvim: require("rustaceanvim.health").check()Checking for Lua dependencies ~- OK [mfussenegger/nvim-dap](https://github.com/mfussenegger/nvim-dap) installed.Checking external dependencies ~- OK rust-analyzer: found rust-analyzer 0.3.1774-standalone (21b06c1be 2023-12-15)- OK Cargo: found - OK rustc: found - OK debug adapter: found codelldb Checking config ~- OK No errors found in config.Checking for conflicting plugins ~- OK No conflicting plugins detected.
How to reproduce the issue
1. Open a rust file with the plugin loaded2. Run `:RustLsp hover actions`3. Select `debug`
Expected behaviour
For the binary to be compiled and for dap to be run.
Actual behaviour
cargo run is executed instead of cargo build this results in No compilation artifacts found error.
The sanitize_command_for_debugging is supposed to replace run with build, but this never occurs. When I added some debugging and logs I found that the sanitize method gets the full table of { cargoArgs={}, cargoExtraArgs={}, executableArgs={}, workspaceRoot='...'} instead of just the cargoArgs list inside the table. The error was found in rust.lua line 33
The minimal config used to reproduce this issue.
-- Minimal nvim config with lazy-- Assumes a directory in $NVIM_DATA_MINIMAL-- Start with---- export NVIM_DATA_MINIMAL=$(mktemp -d)-- export NVIM_APP_NAME="nvim-ht-minimal"-- nvim -u minimal.lua---- Then exit out of neovim and start again.-- Ignore default configlocalconfig_path=vim.fn.stdpath('config')
vim.opt.rtp:remove(config_path)
-- Ignore default pluginslocaldata_path=vim.fn.stdpath('data')
localpack_path=data_path..'/site'vim.opt.packpath:remove(pack_path)
-- bootstrap lazy.nvimdata_path=assert(os.getenv('NVIM_DATA_MINIMAL'), '$NVIM_DATA_MINIMAL environment variable not set!')
locallazypath=data_path..'/lazy/lazy.nvim'localuv=vim.uv---@diagnosticdisable-next-line:deprecatedorvim.loopifnotuv.fs_stat(lazypath) thenvim.fn.system {
'git',
'clone',
'--filter=blob:none',
'git@github.com:folke/lazy.nvim.git',
'--branch=stable',
lazypath,
}
endvim.opt.rtp:prepend(lazypath)
locallazy=require('lazy')
lazy.setup({
{
'mrcjkb/rustaceanvim',
version='^3',
init=function()
-- Configure rustaceanvim herevim.g.rustaceanvim= {}
end,
ft= { 'rust' },
},
-- Add any other plugins needed to reproduce the issue.-- see https://github.com/folke/lazy.nvim#-lazynvim for details.
}, { root=data_path, state=data_path..'/lazy-state.json', lockfile=data_path..'/lazy-lock.json' })
The text was updated successfully, but these errors were encountered:
Tired-Fox
changed the title
Hover actions debug command will run instead of debugging
Hover actions debug command will run instead of buildJan 22, 2024
Neovim version (nvim -v)
v0.9.4
Operating system/version
Window 10 22H2
Output of :checkhealth rustaceanvim
How to reproduce the issue
Expected behaviour
For the binary to be compiled and for dap to be run.
Actual behaviour
cargo run
is executed instead ofcargo build
this results inNo compilation artifacts found
error.The
sanitize_command_for_debugging
is supposed to replacerun
withbuild
, but this never occurs. When I added some debugging and logs I found that the sanitize method gets the full table of{ cargoArgs={}, cargoExtraArgs={}, executableArgs={}, workspaceRoot='...'}
instead of just thecargoArgs
list inside the table. The error was found inrust.lua
line 33The minimal config used to reproduce this issue.
The text was updated successfully, but these errors were encountered: