Anyone else install the VSCode plugin and have the buttons not work? I click Add Server and nothing happens. I'm also seeing a popup when I enable the extension saying "Java version greater than 7 is required to run CFML extension". But when I go to the command line and run

java -version

it spits out: java version "18.0.2" 2022-07-19 Java(TM) SE Runtime Environment (build 18.0.2+9-61) Java HotSpot(TM) 64-Bit Server VM (build 18.0.2+9-61, mixed mode, sharing)

Same. The buttons don't work for me. I saw that error for

cfml.server.create

too.

I'm running CF in a docker container - not sure if that will make any difference or not

If the buttons don't work, you're not even getting far enough for CF compatibility to be an issue, though, right?

not knowing what it's doing, I'm not sure how far it's getting. my very uninformed guess is that js is trying to run a command "from the command line" and it can't find it. Not sure if it has to do with path variables or something. I did follow the pdf and can echo %JAVA_HOME% and it gives me the env var I set. CF itself is running just fine for my app in the browser. not sure 🤷

VS Code extension is compatible with 2016, 2018, 2021. So that's not the issue. The button SHOULD bring up a full dialog that lets you enter server info. If that's not happening, something is going on. Is this on Mac or PC?

PC (windows 10)

I was also having an issue with nothing happening when I clicked the

Create Project

and

Add Server

; ACF2021, Win10. I went away for 30m. When I came and saw your message, I went back to the VSCode instance that I restarted an hour ago and the

Add Server

button is responding. Restarted VSCode and now waiting to see how long it takes to start to UI interactions again.

fwiw, I have the ColdFusion 2018 Update 12 installed

Just started responding, maybe 10 minute warmup.

that's... a while

btw, I never had the popup for the Java version. It's just that the buttons weren't working. I had hover and completion working, though.

long enough I almost wonder if it was idle for the 10 minutes and some event happened just before it started working that finished plugging in all the cables so it could run 🤷

Hey Mith, so there WAS a bug a while back where this was happening. We squashed it like... 100 versions ago, but possibly it may have returned from the dead. Can you please log this as a bug and include that screenshot? I've given the team a heads up to expect it.

you betcha

❤️

My issue looks to be different. I am seeing

WARN UNRESPONSIVE extension host: 'com-adobe-coldfusion.adobe-cfml-lsp' took 100% of 5165.958ms,

messages and each of the four Adobe CFML extension panels has a small single-line progress bar at the top. Those stop moving when an ExtensionHost error occurs:

[Extension Host] TypeError: Cannot read properties of undefined (reading 'toString')
	at c:\Users\theUser\.vscode\extensions\com-adobe-coldfusion.adobe-cfml-lsp-1.0.429\out\extension.js:2:503848
	at c (c:\Users\theUser\.vscode\extensions\com-adobe-coldfusion.adobe-cfml-lsp-1.0.429\out\extension.js:2:504390)
	at c:\Users\theUser\.vscode\extensions\com-adobe-coldfusion.adobe-cfml-lsp-1.0.429\out\extension.js:2:504593
	at g (c:\Users\theUser\.vscode\extensions\com-adobe-coldfusion.adobe-cfml-lsp-1.0.429\out\extension.js:2:504618)
	at c (c:\Users\theUser\.vscode\extensions\com-adobe-coldfusion.adobe-cfml-lsp-1.0.429\out\extension.js:2:504558)
	at c (c:\Users\theUser\.vscode\extensions\com-adobe-coldfusion.adobe-cfml-lsp-1.0.429\out\extension.js:2:504601)
	at c (c:\Users\theUser\.vscode\extensions\com-adobe-coldfusion.adobe-cfml-lsp-1.0.429\out\extension.js:2:504601)
	at c (c:\Users\theUser\.vscode\extensions\com-adobe-coldfusion.adobe-cfml-lsp-1.0.429\out\extension.js:2:504601)
	at c (c:\Users\theUser\.vscode\extensions\com-adobe-coldfusion.adobe-cfml-lsp-1.0.429\out\extension.js:2:504601)
	at g (c:\Users\theUser\.vscode\extensions\com-adobe-coldfusion.adobe-cfml-lsp-1.0.429\out\extension.js:2:504605)
	at Object.t.scanProjects (c:\Users\theUser\.vscode\extensions\com-adobe-coldfusion.adobe-cfml-lsp-1.0.429\out\extension.js:2:503747)
	at c:\Users\theUser\.vscode\extensions\com-adobe-coldfusion.adobe-cfml-lsp-1.0.429\out\extension.js:2:455331
	at t.projectViewer.getChildren (c:\Users\theUser\.vscode\extensions\com-adobe-coldfusion.adobe-cfml-lsp-1.0.429\out\extension.js:2:455579)
	at v.fetchChildrenNodes (c:\Users\theUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:106:19760)
	at v.getChildren (c:\Users\theUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:106:15966)
	at g.$getChildren (c:\Users\theUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:106:11998)
	at s._doInvokeHandler (c:\Users\theUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:95:13708)
	at s._invokeHandler (c:\Users\theUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:95:13390)
	at s._receiveRequest (c:\Users\theUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:95:12159)
	at s._receiveOneMessage (c:\Users\theUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:95:11056)
	at c:\Users\theUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:95:8957
	at w.invoke (c:\Users\theUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:61:145)
	at v.deliver (c:\Users\theUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:61:2266)
	at p.fire (c:\Users\theUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:61:1844)
	at a.fire (c:\Users\theUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:69:18976)
	at c:\Users\theUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:111:34679
	at w.invoke (c:\Users\theUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:61:145)
	at v.deliver (c:\Users\theUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:61:2266)
	at p.fire (c:\Users\theUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:61:1844)
	at a.fire (c:\Users\theUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:69:18976)
	at r._receiveMessage (c:\Users\theUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:69:23563)
	at c:\Users\theUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:69:21097
	at w.invoke (c:\Users\theUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:61:145)
	at v.deliver (c:\Users\theUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:61:2266)
	at p.fire (c:\Users\theUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:61:1844)
	at p.acceptChunk (c:\Users\theUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:69:15807)
	at c:\Users\theUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:69:14937
	at Socket.R (c:\Users\theUser\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:111:13763)
	at Socket.emit (node:events:390:28)
	at addChunk (node:internal/streams/readable:315:12)
	at readableAddChunk (node:internal/streams/readable:289:9)
	at Socket.Readable.push (node:internal/streams/readable:228:10)
	at Pipe.onStreamRead (node:internal/stream_base_commons:199:23)

I can then access the

Server Settings

. They run a tight ship here so my ability to disable security tools, that may or not be causing issues, is severely limited. I've noticed Developer Tools can't reach some servers to pull source maps. I'll do some more digging Monday.

Same error as OP as well. 😞

ERR command 'cfml.server.create' not found: Error: command 'cfml.server.create' not found

But also see this, but I don't know what ip/port it wants.

workbench.desktop.main.jsformatted28185 [Extension Host] java.net.BindException: Address already in use: bind

at java.base/sun.nio.ch.Net.bind0(Native Method)

at java.base/sun.nio.ch.Net.bind(Net.java:555)

at java.base/sun.nio.ch.Net.bind(Net.java:544)

at java.base/sun.nio.ch.AsynchronousServerSocketChannelImpl.bind(AsynchronousServerSocketChannelImpl.java:164)

at java.base/java.nio.channels.AsynchronousServerSocketChannel.bind(AsynchronousServerSocketChannel.java:198)

at com.adobe.coldfusion.ls.CFLanguageServerGateway.startConnection(CFLanguageServerGateway.java:199)

at com.adobe.coldfusion.ls.CFLanguageServerGateway.startLanguageServer(CFLanguageServerGateway.java:175)

at com.adobe.coldfusion.ls.Main.main(Main.java:51)

Please post bugs folks, this error should have been removed and seems to have returned (or it was fixed in some cases and not others). Engineers need to see this is a wide spread issue so they can triage it. I'll let you know if I find out anything internally.

and don't forget to vote 🙂 https://tracker.adobe.com/#/view/CF-4214559

Voted. Am also having the same issue. Windows 10

How do you bring up the devtools console to watch for extension errors? Clicking the "Add server" button in the Cf extension breaks all other extensions, including Git. Using OpenJDK Runtime Environment Temurin-11.0.16+8 (build 11.0.16+8)

In VS Code go to Help > Toggle Developer Tools

I've disabled all other extensions except Adobe CFML and restarted and still get that error above.

There are 40 comments here and 3 votes on this bug tracker issue? And Adobe is saying they can't reproduce the error. Go vote in there.. https://tracker.adobe.com/#/view/CF-4214559

there may be 40 comments in here but the bug in Tracker doesn't match what I'm seeing a couple others in here so I'm not going to vote. No idea how to post a bug for this as there isn't an option to pick VScode plugin.

In their infinite wisdom, they put it under ColdFusion instead of ColdFusion Builder.

I tried this extension on another computer that is licensed to use Oracle Java JRE, same issue. My guess is it's a permissions issue as both Windows computers run under mortal account and not Administrator.

I was told it would be called... deep breath Adobe ColdFusion Builder Extension for VS Code

Their document even calls it that

@saghosh can we get the docs updated to make it easier for folks to find the extension? It seems the name did not come across right?

I guess if that's Step 1 and it doesn't work, I should have expected nothing past that to work. Using Oracle's Java 8 on my other machine actually caused VScode to crash when i'd click on the CF icon in the left side bar. 😒

Do you have java_home set up on that machine?

yep, on both

Interesting, can you please file a bug with the error msg you received, I was under the impression that Java 8 would work, though we recommend Java 11.

Oracle Java 8 on one machine, Adoptium 11 on the other.

I think maybe we should add all the extensions we are using into the bug report CF-4214559. Maybe there is some commonality?

I submitted what I'm seeing as a bug, CF-4214681

It does seem a bit odd that they called it Adobe CFML if cfscript is the future, and CFML is the language and not the IDE, and the VS Code plugin is the next evolution of/replacement for the Eclipse based ColdFusion Builder 🤷‍♂️ Personally, I think it's not too late (or soon!) to rename it to what literally everyone outside Adobe (and I'm guessing nearly everyone inside Adobe) would expect to find it under. Fixing it is a step forward, and leaving it as is would be doubling down on a bad path. I motion that it be changed - anyone second? (because, suddenly, Robert's rules of order or something?!?)

According to Mark, I don't think that is the final name.

I don't think it is, mostly because I'm like. 95% sure that is NOT the name that Adobe Legal green-lit.