calva 2023-09-07 | Slack Archive

MegaMatt18:09:29

After vs code updated today I see this. I’ve removed the file it’s complaining about and actually everything in the .calva directory but still see this when i jack in. Anyone come across this before?

phill18:09:39

Have not seen such a thing. But, had your REPL really accumulated 50 MB of detritus? You could rename-it-to-save-it or maybe review it briskly and consider deleting it.

MegaMatt18:09:12

i deleted the .calva dir but it still complains

MegaMatt18:09:06

well maybe not. i rm’d the file to no avail but i truncated it and now i can jack in.

MegaMatt18:09:17

some run away process got chatty i think.

phill18:09:16

Oh right, now that background threads are correctly output instead of being lost!

💡 2

pez19:09:57

It’s a very strange message.

Christian Pekeler11:09:56

I just had a similar problem. Restarted VSCode (which I hadn’t done in a few days) and couldn’t start the REPL anymore. Nothing in the Calva Connection Log, nothing in the Calva Says, either. But in Extension Host output I found “`2023-09-12 13:53:13.080 [error] CodeExpectedError: cannot open file:///Users/pekeler/Projects/redsky/redsky/.calva/output-window/output.calva-repl. Detail: Files above 50MB cannot be synchronized with extensions.` at n.$tryOpenDocument ()” After deleting the file, it seems to work again. So, same problem, but I didn’t get the graphical notification.

2023-09-07

Channels