Clojurians Log v2

Have you tried re-installing it?

Oh, no. Let me check.

Yea just uninstalled/restarted extensions and reinstalled. I get the same error for running other commands as well

I get the same, but only with the release build. You should be able to downgrade and get the commands back. I’ll see how quickly I can fix this.

Oh perfect I didn’t know I could install a specific version, that fixed up the issue (after restarting code). Very much appreciated thank you 🙏 I use user scripts every day so I really appreciate y’all’s work and quick help 🙏

It’s great to hear that Joyride is being put to use! I’d love to hear what your use cases are.

It’s so strange with this error. Our integration tests should guard against it, but they run fine…

My primary use case is just starting up our full stack app for development! I previously used emacs and I had tried to switch to Code a few times but I couldn’t reliably get jack-in working for our custom start up and with the proper environment variables. I use a custom script to read env vars and start up the repl and run custom code on startup as well

Sweet. Calva can’t cover all bases, but Joyride can. 😃

I guess that means I should not reload my VS Code window because I'll get a borked Joyride? 🙂

I’ve found the fix now, I am pretty sure, so you should be able to reload soon.

I just want to create a way to catch this particular error in my integration testing. So holding off the release a few more minutes.

Joyride v0.0.65 fixes the problem, @seancorfield @brianbadahdah