fix: vscode workspaceState bug workaround

[Anonymous941]

Description

See #301 for the writeup, microsoft/vscode@06c07d2 introduces a subtle backwards compatibility issue which causes the extension to be unusable

Motivation and Context

Fixes #301, which makes the extension completely unusable in VS Code versions after 1.96.4

Testing

This has been tested on VS Code version 1.101.14098

Screenshots (if appropriate)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• My code follows the code style of this project
• My change requires a change to the documentation
• I have updated the documentation accordingly
• I have read the README document
• I have added tests to cover my changes
• All new and existing tests passed
• My commit message follows Conventional Commit Guideline

License

• By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[tydonelson]

Thanks the deep investigation and fix, apologies we didn't get to it.

[Anonymous941]

No problem, we all get busy sometimes. Glad I could fix it

[milasantacruz]

Hi. im still experiencing this issue, running in VScode 1.101.2 and Ask toolkit 2.16.0

[Anonymous941]

@milasantacruz Strange, can you share the relevant extension logs? You can do this by pressing CTRL+Shift+P, choosing Developer: Export Logs... and checking only Extension Host. You may need to disable other extensions since they could spam the log, and every extension error is on the same log for some reason

[milasantacruz]

@Anonymous941
thanks for replying. those are my logs from the steps you suggest:

[Anonymous941]

That log doesn't seem contain the error message. Can you try opening the project in order to get the "Workspace is not a valid skill project" popup, then afterwords exporting the logs?

[milasantacruz]

That's exactly what i did. i notice that in the logs does not appear any error message, so i start the vs code many times and trigger the refresh button in the UI of the toolkit to show up the message error in the popup. but the logs doesn't reflect an error

[Anonymous941]

Got it. To be honest I'm not really sure how to fix this, since the logs aren't being very helpful here. The way I fixed the old problem was by adding special logging in VSCode's source code around the function that changed after using git bisect.

If you haven't already, can you try disabling all other extensions and seeing if the error still occurs?