Error: vim-ultest encountered an unknown error on startup
See original GitHub issueDescribe the bug When I open my js test file (jest) I get this message at the status bar:
Error: vim-ultest encountered an unknown error on startup, check v:exception
I tried to run Ultest
command anyways but nothing happens.
NVIM v0.6.1
Build type: Release
macOs Monterrey 12.1
No logs created.
To Reproduce I’m just opening the file and running the command.
Expected behavior
Not to see an error message at the status bar and see the tests running when I put Ultest
command.
Screenshots
Additional context
TestFile
works good.
Issue Analytics
- State:
- Created 2 years ago
- Comments:13 (6 by maintainers)
Top Results From Across the Web
Windows Update encountered an unknown error. (Code ...
I have tried downloading the update and installing it with a clean boot, just to get the message "This update is not applicable...
Read more >iOS update and restore errors - Apple Support
If your device couldn't be restored and you get a message that "an unknown error occurred [error number]," use these steps.
Read more >"Unknown Error" Message Starting Visual Studio 2017 ...
I've installed VS 2017 Enterprise on a Win 7 Ultimate machine. The application was installed while logged on as Adminstrator.
Read more >An Unknown Error Has Been Encountered
My client's situation is that the implementation uses the BarTender .Net SDK (10.1 SR2) within a custom WCF service. All parameters are...
Read more >Fix unknown error issues in Illustrator - Adobe Support
ai format. Start using the workarounds in the order mentioned below to fix the problem. Try to save the file after you perform...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
See ':h g:ultest_pass_sign`, the docs list all of the signs you can change
You need to run that after installing, normally there is a more helpful message but it matched the English message which is why you didn’t see it. It will now instead match the error code