Receiving "disconnect" message

[HopperTech]

Please select the area your bug applies to. (Multiple selections are Possible. You can leave blank if you're not sure.)

• Workspace. VSCode workspace, vaults, Intellisense/autocomplete, Dendron settings
• Lookup. Dendron's Lookup Command
• Views. Dendron Preview, Tree View, Side Panels in the UI
• Schema. Dendron Schemas
• Pod. Data import from / export to Dendron
• Publish. External Site Publish
• Markdown. Markdown features, such as syntax support and features

Describe the bug

Tried opening my workspace this morning and started receiving a "disconnect" message.
Have tried the following without success:

• reinstalling dendron
• starting a new workspace
• clearing vscode cache
• restarting computer

To Reproduce

Steps to reproduce the behavior:

Not sure

Expected behavior

workspace to open as expected

Screenshots

If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information)

• OS: [e.g. iOS] Win 10
• Browser (if with published websites; include version): [e.g. chrome, safari] N/A
• Versions (all that apply to bug):
  • Dendron Extension: v0.102.0
  • VS Code version: 1.70.0-insider
  • Dendron CLI:

Additional context

Add any other context about the problem here.

Dendron Log file

Please attach the output of > Dendron:Dev: Open Logs here
dendron.log

[HopperTech]

This is working in vscode version 1.69.0 (not insiders)

[thelumberjhack]

I am having the same issue on both win11 and MacOS with VSCode Insiders 1.70.0:

I don't know if it's related but I am getting this error too (unrelated to Dendron): microsoft/vscode#154569

[kevinslin]

Thanks for the report - this seems to be an issue with insiders. Looking into what we can do about it on our side

[kevinslin]

This looks like a regression on the latest build of vscode-insider. submitted microsoft/vscode#154886 and will wait on updates

[kevinslin]

meanwhile, adding a workaround that will be live with the v103 release tomorrow!

[kevinslin]

if you would like to have this working ahead of time, you can downgrade to 1.69.0 of insider by following instructions in https://stackoverflow.com/questions/69576354/is-it-possible-to-downgrade-vscode-insiders-download-older-insider-builds

[thelumberjhack]

if you would like to have this working ahead of time, you can downgrade to 1.69.0 of insider by following instructions in https://stackoverflow.com/questions/69576354/is-it-possible-to-downgrade-vscode-insiders-download-older-insider-builds

That's what I did right away. Thanks @kevinslin

[HopperTech]

This is working now, thank you for addressing even though not technically an issue with your app. Guess that is part of the fun building on top of someone else's environment.

[kevinslin]

will keep this open until it is resolved. it looks like vscode team is aware of this and working on a fix