search

nvim-neotest / neotest-jest

MIT License
118 stars 79 forks source link

EBADF: bad file descriptor #32

Closed mrjones2014 closed 2 years ago

mrjones2014 commented 2 years ago

My full Neotest config:

require('neotest').setup({
  discovery = { enabled = false },
  adapters = {
    require('neotest-plenary'),
    require('neotest-rust'),
    require('neotest-jest')({
      jestCommand = 'pnpm jest',
      cwd = require('lsp.utils').typescript_root_dir,
    }),
  },
})

When I run require('neotest').run.run() in a Typescript jest file I get a popup saying Vim:E729: using Funcref as a String and the following error output

Error executing luv callback:
...ck/packer/start/plenary.nvim/lua/plenary/async/async.lua:14: The coroutine failed with this message: ...eotest/lua/neotest/client/strategies/integrated/init.lua:32: EBADF: bad file descriptor
stack traceback:
        [C]: in function 'error'
        ...ck/packer/start/plenary.nvim/lua/plenary/async/async.lua:14: in function 'callback_or_next'
        ...ck/packer/start/plenary.nvim/lua/plenary/async/async.lua:40: in function <...ck/packer/start/plenary.nvim/lua/plenary/async/async.lua:39>
Press ENTER or type command to continue
mrjones2014 commented 2 years ago

if it's relevant, I'm trying to run tests in a monorepo using pnpm workspaces.

mrjones2014 commented 2 years ago

my cwd config was bad. my fault.