FHIR Chat · Atom not showing CQL --> Execute · cql

Stream: cql

Topic: Atom not showing CQL --> Execute


view this post on Zulip Aziz Boxwala (Mar 22 2021 at 20:12):

I cannot get Atom to show the CQL --> Execute context menu item. It shows the "View ELM" menu item though. I am running Atom 1.55.0, language-cql plugin 2.9.0 on Windows 64. Any help is welcome.

view this post on Zulip Aziz Boxwala (Mar 23 2021 at 01:41):

Tagging @JP and @Bryn Rhodes in case you know what might be causing the issue.

view this post on Zulip Peter Muir (Mar 23 2021 at 14:16):

Hi Aziz I use on Ubuntu and MacOS. It needs packages: atom-ide-iu 0.13.0, ide-java 0.9.1, language-cql 2.9.0 and project created with correct directory profile from CQLramework. (there are pathways for FHIR401 from previous Connectathons and more recent from January which will be path to future.) Slack me if package install doesn't get it running .

view this post on Zulip Aziz Boxwala (Mar 23 2021 at 14:37):

I had the ide-ui and added the ide-java package. Still did not work @Peter Muir

view this post on Zulip Peter Muir (Mar 23 2021 at 14:41):

check email

view this post on Zulip Bryn Rhodes (Mar 23 2021 at 16:47):

I am running that exact same set up @Aziz Boxwala , can you open the developer tools (Ctrl-Shift-I) and see if there are any errors messages being reported?

view this post on Zulip Bryn Rhodes (Mar 23 2021 at 16:48):

And what Java runtime are you using? I'm running adoptOpenJDK.

view this post on Zulip Dave Carlson (Mar 23 2021 at 16:50):

I had a similar issue a few weeks ago and fixed it by uninstalling and re-installing the Atom plugin.

view this post on Zulip Aziz Boxwala (Mar 23 2021 at 17:00):

@Bryn Rhodes this is the error

view this post on Zulip Aziz Boxwala (Mar 23 2021 at 17:02):

@Bryn Rhodes I will checkout the jdk config. I have at least two versions installed and maybe that is causing a problem. This is the error I see in the console:

RequestError
cause: Error: options.uri is a required argument at Request.init (C:\Users\boxwa\.atom\packages\language-cql\node_modules\request\request.js:231:31) at Request.RP$initInterceptor [as init] (C:\Users\boxwa\.atom\packages\language-cql\node_modules\request-promise-core\configure\request2.js:45:29) at new Request (C:\Users\boxwa\.atom\packages\language-cql\node_modules\request\request.js:127:8) at request (C:\Users\boxwa\.atom\packages\language-cql\node_modules\request\index.js:53:10) at Function.head (C:\Users\boxwa\.atom\packages\language-cql\node_modules\request\index.js:61:12) at C:\Users\boxwa\.atom\packages\language-cql\lib\main.js:144:19 at processTicksAndRejections (internal/process/task_queues.js:89:5)
rawStack: Array(7)
0: CallSite {}
1: CallSite {}
2: CallSite {}
3: CallSite
__proto__: Object
4: CallSite {}
5: CallSite {}
6: CallSite {}
length: 7
__proto__: Array(0)
message: "options.uri is a required argument"
stack: "Error: options.uri is a required argument↵    at Request.init (C:\Users\boxwa\.atom\packages\language-cql\node_modules\request\request.js:231:31)↵    at Request.RP$initInterceptor [as init] (C:\Users\boxwa\.atom\packages\language-cql\node_modules\request-promise-core\configure\request2.js:45:29)↵    at new Request (C:\Users\boxwa\.atom\packages\language-cql\node_modules\request\request.js:127:8)↵    at request (C:\Users\boxwa\.atom\packages\language-cql\node_modules\request\index.js:53:10)↵    at Function.head (C:\Users\boxwa\.atom\packages\language-cql\node_modules\request\index.js:61:12)↵    at C:\Users\boxwa\.atom\packages\language-cql\lib\main.js:144:19↵    at processTicksAndRejections (internal/process/task_queues.js:89:5)"
__proto__: Object
error: Error: options.uri is a required argument at Request.init (C:\Users\boxwa\.atom\packages\language-cql\node_modules\request\request.js:231:31) at Request.RP$initInterceptor [as init] (C:\Users\boxwa\.atom\packages\language-cql\node_modules\request-promise-core\configure\request2.js:45:29) at new Request (C:\Users\boxwa\.atom\packages\language-cql\node_modules\request\request.js:127:8) at request (C:\Users\boxwa\.atom\packages\language-cql\node_modules\request\index.js:53:10) at Function.head (C:\Users\boxwa\.atom\packages\language-cql\node_modules\request\index.js:61:12) at C:\Users\boxwa\.atom\packages\language-cql\lib\main.js:144:19 at processTicksAndRejections (internal/process/task_queues.js:89:5)
rawStack: (7) [CallSite, CallSite, CallSite, CallSite, CallSite, CallSite, CallSite]
message: "options.uri is a required argument"
stack: "Error: options.uri is a required argument↵    at Request.init (C:\Users\boxwa\.atom\packages\language-cql\node_modules\request\request.js:231:31)↵    at Request.RP$initInterceptor [as init] (C:\Users\boxwa\.atom\packages\language-cql\node_modules\request-promise-core\configure\request2.js:45:29)↵    at new Request (C:\Users\boxwa\.atom\packages\language-cql\node_modules\request\request.js:127:8)↵    at request (C:\Users\boxwa\.atom\packages\language-cql\node_modules\request\index.js:53:10)↵    at Function.head (C:\Users\boxwa\.atom\packages\language-cql\node_modules\request\index.js:61:12)↵    at C:\Users\boxwa\.atom\packages\language-cql\lib\main.js:144:19↵    at processTicksAndRejections (internal/process/task_queues.js:89:5)"
__proto__: Object
message: "Error: options.uri is a required argument"
name: "RequestError"
options: {method: "HEAD", callback: ƒ, transform: ƒ, simple: true, resolveWithFullResponse: false, …}
rawStack: (12) [CallSite, CallSite, CallSite, CallSite, CallSite, CallSite, CallSite, CallSite, CallSite, CallSite, CallSite, CallSite]
response: undefined
stack: "RequestError: Error: options.uri is a required argument↵    at new RequestError (C:\Users\boxwa\.atom\packages\language-cql\node_modules\request-promise-core\lib\errors.js:14:15)↵    at Request.plumbing.callback (C:\Users\boxwa\.atom\packages\language-cql\node_modules\request-promise-core\lib\plumbing.js:87:29)↵    at Request.RP$callback [as _callback] (C:\Users\boxwa\.atom\packages\language-cql\node_modules\request-promise-core\lib\plumbing.js:46:31)↵    at self.callback (C:\Users\boxwa\.atom\packages\language-cql\node_modules\request\request.js:185:22)↵    at Request.emit (events.js:200:13)↵    at Request.init (C:\Users\boxwa\.atom\packages\language-cql\node_modules\request\request.js:231:17)↵    at Request.RP$initInterceptor [as init] (C:\Users\boxwa\.atom\packages\language-cql\node_modules\request-promise-core\configure\request2.js:45:29)↵    at new Request (C:\Users\boxwa\.atom\packages\language-cql\node_modules\request\request.js:127:8)↵    at request (C:\Users\boxwa\.atom\packages\language-cql\node_modules\request\index.js:53:10)↵    at Function.head (C:\Users\boxwa\.atom\packages\language-cql\node_modules\request\index.js:61:12)↵    at C:\Users\boxwa\.atom\packages\language-cql\lib\main.js:144:19↵    at processTicksAndRejections (internal/process/task_queues.js:89:5)"
__proto__: Error
constructor: ƒ RequestError(cause, options, response)
__proto__: Object```

view this post on Zulip Aziz Boxwala (Mar 23 2021 at 17:04):

I am testing with the example here with no changes: https://github.com/cqframework/content-ig-walkthrough

view this post on Zulip Aziz Boxwala (Mar 23 2021 at 22:16):

@Dave Carlson Thank you for the tip. I reinstalled the plugin after cleaning up my Java-related environment variables and that worked.


Last updated: Apr 12 2022 at 19:14 UTC