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 Jul 15, 2023. It is now read-only.
The codelens for references uses the guru tool behind the scenes to provide references.
When guru fails, the codelens shows "0 references" instead of alluding to the fact that the tool has failed behind the scenes
The console shows failures from guru with details on the command being called with args as well as a call stack. The call stack is related to node and the child process that was spawned for guru and is pointless
The codelens would say "Error finding references" instead of "0 references" if there was error in running the guru tool
When there is error running the guru tool, the console will show the command and the args being passed as before. The call stack related to node and child process will not be shown
The codelens for references uses the
guru
tool behind the scenes to provide references.When
guru
fails, the codelens shows "0 references" instead of alluding to the fact that the tool has failed behind the scenesThe console shows failures from
guru
with details on the command being called with args as well as a call stack. The call stack is related to node and the child process that was spawned forguru
and is pointlesscc @JeffreyRichter
The text was updated successfully, but these errors were encountered: