You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 3, 2025. It is now read-only.
It often happens that nim check, invoked by VSCode, hangs for whatever reason. This results in several hanging processes consuming lots of CPU (each fully occupies single core in my case):
I think it would make sense for VSCode not to invoke more than one nim check at a time, and kill previous process when invoking a new one.
The text was updated successfully, but these errors were encountered:
It often happens that

nim check
, invoked by VSCode, hangs for whatever reason. This results in several hanging processes consuming lots of CPU (each fully occupies single core in my case):I think it would make sense for VSCode not to invoke more than one
nim check
at a time, and kill previous process when invoking a new one.The text was updated successfully, but these errors were encountered: