revealing a non-existing tree item results in an (unhelpful) error

[weinand]

testing #52806:

• use https://github.com/weinand/vscode-processes
• uncomment the console.log in extension.ts:310
• set a breakpoint in extension.ts:310
• F5
• run "Show Processes View" command
• wait a few seconds

If no error occurs (and the breakpoint is not hit), collapse/expand the process view or hide/unhide it.

Observe: you hit the breakpoint and the error message refers to the internal id of the treeitem.

Without the error handler the following massive error shows up in the console:

IMO the usefulness of the error is questionable.
Since it can always happen that a revealed item has dropped from the tree, installing an error handler seems to be mandatory. But what can be done in the handler other than suppressing the error?

[sandy081]

Makes sense. Just logging the error and returning a successful promise is good enough.

[JacksonKearl]

Do you know why I'd be unable to get any breakpoints to verify when debugging the vscode-extension process?

Edit: turns out process needs to be activated for the brakepoint to activate.