Goes away if if I add more chars to var, add space inside vector, move vector to same line as docstring, or remove docstring. I checked it out with the Scopes Inspector, but that shows the same scopes as normal, and even lists the correct fg/bg colors, making no mention of white or black colors.

I doubt Calva has anything to do with this. As always, I could be wrong. Can you run an Extension Bisect and see what it gives?

Great tip! Thanks. Caused by Todo Tree, which apparently was seeing [ ] and [x] as checkbox representations of todos. --- But I was also able to use Extension Bisect it to figure out that Calva has been causing me this error:

[Extension Host] (node:350285) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
(Use `code --trace-deprecation ...` to show where the warning was created)

The suggested code --trace-deprecation has never worked on my system, but the Bisect pointed the finger clearly at Calva.

https://github.com/BetterThanTomorrow/calva/issues/1939

We've had that with Calva from day one 😃 Never figured it out. If you do, please feel invited to PR it!

I assume that means you already tried running Code with trace-deprecation flag?

It was a very long time since I had a look. Don't remember what I have tried or not.

It hasn't bothered me enough, I guess. 😃

On Arch, the flag does nothing. 😞 But when you have a chance, just try starting Code from command line with that flag added, and see if it points to anything useful.

I don't know what the actual security issue is, but when something is deprecated for security reasons, its usually a good idea to raise it above "it bothers me". 😄

¯\(ツ)/¯

Are we keeping Node modules up to date? I wonder if just updating some of them could make this just go away.

It has happened that we update dependencies.

I think it is extract-zip, updated the issue with some info.

👍 I'll test that out later.