Andy Freeland

> can you clarify whether you want this because of celery or something else? I was reviewing the open issues while migrating away from the old raven library. :) We...

This seems fixed with version 2.5.2 of the `vagrant-vmware-fusion` plugin. Works for me and also https://github.com/mitchellh/boot2docker-vagrant-box/issues/48#issuecomment-51965835

> Hi @rouge8 I added tests for the new functionality. I also had to install `cargo nextool` now in the CI because the new tests require them when testing the...

Yes, I plan to review it. Unfortunately I don’t write much Rust these days so it’s not super pressing…

1. It's a private project unfortunately. 2. neotest config: ```lua -- Neotest local neotest = require("neotest") neotest.setup({ discovery = { enabled = true }, adapters = { require("neotest-python")({ args =...

I can't reproduce it with the test package unfortunately. I decided to open source the repo I was testing with: https://github.com/rouge8/wanikani-apprentice/blob/main/src/main.rs#L793

> Hey @rouge8, > > thanks for sharing your project. You were onto something, it actually was a problem with the `M._binary_name()` function. I forgot the (prob. not that uncommon)...

I'm still seeing errors in https://github.com/rouge8/wanikani-apprentice/blob/main/src/wanikani.rs: ``` || Error executing luv callback: || ...andy/.local/share/nvim/plugged/neotest/lua/nio/tasks.lua:95: Async task failed without callback: The coroutine failed with this message: || ...ndy/projects/neotest-rust/lua/neotest-rust/discovery.lua:323: bad argument #1...

With `tests/minimal_init.vim` and nvim 0.9.5 on macOS nvim crashes and exits with code 134 when I try to run the tests 🙃

> > Can you reproduce the issue with the same setup? > > ??? Can you create a Dockerfile that installs the appropriate nvim, cargo nextest, etc.? If you do...