Closed DrMuir closed 2 years ago
Having similar problems in Windows 10 and 11 environments, even while working in Docker environment.
After I deleted plug-in v0.1.5 and reinstalled v0.1.4, it is running appropriately again. Presumably, I am missing some other requirement but will stay old school for now.
@DrMuir could you provide more information on what is not working properly? I have been able to run several of the measures in the https://github.com/cqframework/ecqm-content-r4-2021 IG successfully using v0.1.5.
Same thing with me, Windows 11.
It would take a long time upon startup to initialize and recognize errors/issues, and only simple measures would work with Execute CQL.
One bit of new weird behavior I noticed was that it would flag CQL libraries as duplicate across different projects. For example, a copy of FHIRHelpers in one project would be considered a duplicate of FHIRHelpers in a completely different project if they were both loaded in the project explorer at the same time.
Upgraded to VSCode 1.70 on Windows 10 this morning (2022/08/15). Started getting startup messages from V0.1.5 of CQL extension: Error: Invalid or corrupt jarfile c:\Users\fadrian.vscode\extensions\cqframework.cql-0.1.5\dist\jars\cql-ls-service-1.5.7.jar [Info - 8:19:12 AM] Connection to server got closed. Server will restart.
After removing the CQL extension from the .vscode/extensions folder and re-installing the extension, things seem to work again.
Still having issues even after removing CQL extension and reinstalling. On Windows 10 On VS Code 1.70.2
Highlighting works, but validation will not work.
It automatically upgraded to 0.1.6 pre-release version and seemed to work well. But the next day, after I removed older versions of the extension and a restart, it stopped working. "Execute CQL" seems to do nothing -- no results file opens, and no java thread is started in the task manager. I've tried uninstalling the extension and re-installing, and the behavior is unchanged. I have confirmed that the 1.5.8 jar is in place for 0.1.6.
On the bright side, 0.1.5 is working and seems to be performing somewhat better. I can't get VS Code to stick to the 0.1.4 version -- it keeps automatically going to 0.1.5.
These issues should all be addressed with the 0.2.0 release
Hey Stan. I uninstalled VScode 0.1.5 plug-in and went back to 0.1.4 which resolved run issue. I suspect there is something out of alignment with the CQL-language server at this time.
Peter Muir | MD ABFM FCFP Informatics ESAC, now proudly part of ICF Note new email: @.**@.> icf.comhttps://www.icf.com/
From: JSRankins @.> Sent: Thursday, August 11, 2022 5:53 PM To: cqframework/vscode-cql @.> Cc: Muir, Peter @.>; Author @.> Subject: Re: [cqframework/vscode-cql] CQL Plug-in issue after update 8/10/22 (Issue #17)
Having similar problems in Windows 10 and 11 environments, even while working in Docker environment.
— Reply to this email directly, view it on GitHubhttps://github.com/cqframework/vscode-cql/issues/17#issuecomment-1212533461, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJBBZR4VSXFSVWIF6FPDS6TVYVY55ANCNFSM56JQD6JA. You are receiving this because you authored the thread.Message ID: @.***>
VScode (Linux/Ubuntu) not working properly on previously working measures/data in local r4-2021 and QI-Core 2022 since CQL plug-in updated 8/10. Released on 9/24/2021, 16:40:12 Last updated 8/10/2022, 12:09:45 Identifier cqframework.cql
Will try delete and reload of plug.