Latency with VS Code 1.93 for "Import and Compile"

Question

Question

Maxime LACH · Sep 19

Hello,

Since version 1.93 of VS Code, the “import and compile” process has been very slow (more than an hour).
Have you encountered this issue and do you know how to resolve it?

Thank you,

Maxime

Product version: Ensemble 2018.1

Discussion (10)3

Log in or sign up to continue

John Murray · Sep 19

Please follow this issue:

https://github.com/intersystems-community/vscode-objectscript/issues/1428

1 0

John Murray · Sep 19

Currently the workaround is to downgrade your VS Code to 1.92.2. More info here:

https://code.visualstudio.com/docs/supporting/faq#_how-do-i-opt-out-of-v...

1 0

score 0 · Answer 1 · 2024-09-19T09:26:28-04:00

Maxime LACH · Sep 19

Thank you for the link

0 0

score 0 · Answer 2 · 2024-09-19T09:27:19-04:00

Maxime LACH · Sep 19

Thank you for the link

0 0

score 0 · Answer 3 · 2024-09-19T09:26:11-04:00

Maxime LACH · Sep 19

Yes, this is the only solution we have found
Thanks

0 0

score 0 · Answer 4 · 2024-09-20T12:14:05-04:00

Anyone suffering from this and who hasn't downgraded to VS Code 1.92.2, or who has but is willing to upgrade to 1.93 again, please see https://github.com/intersystems-community/vscode-objectscript/issues/142...

Unless we get adverse reports about that beta VSIX we plan to publish a non-beta build of it on Marketplace early next week.

score 0 · Answer 5 · 2024-09-24T11:12:24-04:00

John Murray · Sep 24

A new version of the ObjectScript was published on Marketplace yesterday to fix this issue.

0 0

score 0 · Answer 6 · 2024-09-25T08:32:05-04:00

I upgraded to the new beta that uses the proposed apis (v2.12.9-beta.1), and when I reconnected to the server, it took quite some time (5-10 minutes) before I could get to work. Since then, performance has been normal. Is there some new feature that indexes classes/routines locally or something? I couldn't find anything in the usual logs that indicated what was going on.

score 0 · Answer 7 · 2024-09-25T13:00:53-04:00

No, nothing else new in it. Were you able to connect but not work? Or wasn't it possible to connect? If the latter, perhaps the server had run out of licenses.

score 0 · Answer 8 · 2024-09-25T23:48:08-04:00

Oh yes, it finally settled down and worked normally, but it seemed to be spending a lot of time talking to the servers before displaying the package listing. The servers are on AWS and I'm connected via a VPN, but my connection is quite fast for a home office and I've never noticed that before.

I've also exited and relaunched VS Code since without any significant delay, so it must've been a one-off.