Selene linter issue: Unknown system error -86

[bootdme]

I am trying to use the selene linter, but I get this issue every time I load up .lua files.

[DEBUG Thu Feb 23 23:28:49 2023] ...y/null-ls.nvim/lua/null-ls/helpers/generator_factory.lua:320: spawning command "selene" at /Users/bootdme/.config/nvim/lua/modules/configs/completion with args { "--display-style", "quiet", "-" }

[WARN Thu Feb 23 23:28:49 2023] ...e/nvim/site/lazy/null-ls.nvim/lua/null-ls/generators.lua:94: failed to run generator: ...l/share/nvim/site/lazy/null-ls.nvim/lua/null-ls/loop.lua:165: failed to spawn command selene: Unknown system error -86: Unknown system error -86

Same issue arises with shellcheck when I load up .sh files.

What is the issue with this?

Thanks

[jose-elias-alvarez]

No idea, I've never seen this error before. Can you successfully run these linters from the command line? Do you have the same issue with all sources?

[bootdme]

Yes I can since I also installed selene using brew because I thought originally that would solve the issue, but it didn't.

nvim
├── nvim/init.lua
├── nvim/lazy-lock.json
├── nvim/lua
│   ├── nvim/lua/core
│   │   ├── nvim/lua/core/auto.lua
│   │   ├── nvim/lua/core/boot.lua
│   │   ├── nvim/lua/core/clip.lua
│   │   ├── nvim/lua/core/dirs.lua
│   │   ├── nvim/lua/core/func.lua
│   │   ├── nvim/lua/core/global.lua
│   │   ├── nvim/lua/core/lazy.lua
│   │   ├── nvim/lua/core/opts.lua
│   │   └── nvim/lua/core/sets.lua
│   └── nvim/lua/modules
│       ├── nvim/lua/modules/configs
│       │   ├── nvim/lua/modules/configs/completion
│       │   │   ├── nvim/lua/modules/configs/completion/autopairs.lua
│       │   │   ├── nvim/lua/modules/configs/completion/cmp.lua
│       │   │   ├── nvim/lua/modules/configs/completion/lsp
│       │   │   │   ├── nvim/lua/modules/configs/completion/lsp/bashls.lua
│       │   │   │   ├── nvim/lua/modules/configs/completion/lsp/emmet_ls.lua
│       │   │   │   ├── nvim/lua/modules/configs/completion/lsp/eslint.lua
│       │   │   │   ├── nvim/lua/modules/configs/completion/lsp/jsonls.lua
│       │   │   │   ├── nvim/lua/modules/configs/completion/lsp/lua_ls.lua
│       │   │   │   ├── nvim/lua/modules/configs/completion/lsp/marksman.lua
│       │   │   │   ├── nvim/lua/modules/configs/completion/lsp/null-ls.lua
│       │   │   │   ├── nvim/lua/modules/configs/completion/lsp/sqlls.lua
│       │   │   │   └── nvim/lua/modules/configs/completion/lsp/vimls.lua
│       │   │   ├── nvim/lua/modules/configs/completion/lspconfig.lua
│       │   │   ├── nvim/lua/modules/configs/completion/luasnip.lua
│       │   │   └── nvim/lua/modules/configs/completion/mason-tool-installer.lua
│       │   └── nvim/lua/modules/configs/ui
│       │       └── nvim/lua/modules/configs/ui/treesitter.lua
│       └── nvim/lua/modules/plugins
│           ├── nvim/lua/modules/plugins/completion.lua
│           └── nvim/lua/modules/plugins/ui.lua
├── nvim/selene.toml
└── nvim/stylua.toml

This is how my nvim is setup in my .config directory.

Is it because my .toml files aren't in the root directory? I looked at your dots to try and mimic to see if that would resolve the issue but it didn't.

EDIT: I forgot to mention that this issue is occurring when I am inside my nvim configuration

[jose-elias-alvarez]

So it only occurs in your configuration directory? Do Lua files elsewhere works? If you can put together a way for me to reproduce this I can investigate further, but I doubt the issue is related to the specific directory structure.

[bootdme]

The selene linter does not work in other directories (works perfectly fine through CLI). The interesting thing that occurs as well is my b.formatting.stylua and b.diagnostics.selene don't have any extra arguments attached to them inside my null-ls.lua and my stylua.toml is read with null-ls, but not selene.toml.

EDIT: Just tried using stylus inside a different directory, but used the stylua.toml from inside my ~/.config/nvim. I assume this is a nvim issue rather than null-ls?

[bootdme]

UPDATE: selene was installed via both mason and brew. After uninstalling selene from mason, null-ls was able to read selene from brew. The issue will appear if selene is not installed via brew and installed by Mason.

[jose-elias-alvarez]

I see, glad you figured out. Curious to know if the Selene binary from Mason has the same issue when run directly from the command line, but either way I suspect the issue is not something we can do anything about.