Repair Komodo error running activestate.yaml script

wblake · March 15, 2022, 6:01pm

Attempting in Komodo to run the activationMessage script from activestate.yaml leads to then enclosed error about the script language even though Perl remains installed in the ActiveState project that launched Komodo. I will enclose the error message, screenshot, and the trouble shooting log file output.
Thanks,
Wil B

Error message text.
“The language for this script is not supported or not available on your system. Attempted script execution with perl. Please configure the ‘language’ field with an available option (one, or more of : bash, sh, batch, powershell, perl, python3,python2.ruby)”
Screenshot of Error Message

Tail of The log file
– EXCEPTION START –
TypeError: command.isExecutable is not a function

stack
getCommandStr@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/commonjs/sdk/system/child_process/subprocess.js:412:16
subprocess_win32@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/commonjs/sdk/system/child_process/subprocess.js:1043:18
subprocess.call@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/commonjs/sdk/system/child_process/subprocess.js:456:20
initialize@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/commonjs/sdk/system/child_process.js:45:14
constructor@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/commonjs/sdk/core/heritage.js:145:23
spawn@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/commonjs/sdk/system/child_process.js:153:10
this.run@chrome://komodo/content/sdk/shell.js:170:23
runSh@chrome://state/content/js/sdk/tool.js:310:20
this.scripts@chrome://state/content/js/sdk/tool.js:498:9
getScripts@chrome://state/content/js/button.js:282:13
xtk.domutils.fireEvent@chrome://xtk/content/domutils.js:157:5
project_openProjectFromURL/<@chrome://komodo/content/project/projectManager.js:1588:9
– EXCEPTION END –
[2022-03-15 13:59:39,706] [ERROR] ko-shell: Error during process execution
– EXCEPTION START –
TypeError: command.isExecutable is not a function
stack
getCommandStr@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/commonjs/sdk/system/child_process/subprocess.js:412:16
subprocess_win32@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/commonjs/sdk/system/child_process/subprocess.js:1043:18
subprocess.call@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/commonjs/sdk/system/child_process/subprocess.js:456:20
initialize@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/commonjs/sdk/system/child_process.js:45:14
constructor@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/commonjs/sdk/core/heritage.js:145:23
spawn@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/commonjs/sdk/system/child_process.js:153:10
this.run@chrome://komodo/content/sdk/shell.js:170:23
runSh@chrome://state/content/js/sdk/tool.js:310:20
activate@chrome://state/content/js/sdk/tool.js:664:9
this.activate@chrome://state/content/js/sdk/tool.js:717:9
this.reactivate@chrome://state/content/js/sdk/tool.js:875:13
activationHandler@chrome://state/content/js/sdk/tool.js:868:9
xtk.domutils.fireEvent@chrome://xtk/content/domutils.js:157:5
– EXCEPTION END –
[2022-03-15 13:59:39,707] [ERROR] tool.js: Process exited with code ‘-1’. Error:
Traceback from ERROR in ‘tool.js’ logger:
Logger.prototype.error@chrome://komodo/content/sdk/logging.js:411:27
getDefaultCallbacks/<.onFail@chrome://state/content/js/sdk/tool.js:176:38
activate/callbacks.onFail@chrome://state/content/js/sdk/tool.js:656:17
runSh/<@chrome://state/content/js/sdk/tool.js:336:17
emit@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/commonjs/sdk/event/core.js:96:9
handleError@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/commonjs/sdk/system/child_process.js:108:7
initialize/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/commonjs/sdk/system/child_process.js:92:19
delay/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/commonjs/sdk/lang/functional/concurrent.js:38:20
notify@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/commonjs/sdk/timers.js:40:9

[2022-03-15 13:59:39,707] [ERROR] ko-shell: Error during process execution
– EXCEPTION START –
TypeError: command.isExecutable is not a function

stack
getCommandStr@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/commonjs/sdk/system/child_process/subprocess.js:412:16
subprocess_win32@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/commonjs/sdk/system/child_process/subprocess.js:1043:18
subprocess.call@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/commonjs/sdk/system/child_process/subprocess.js:456:20
initialize@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/commonjs/sdk/system/child_process.js:45:14
constructor@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/commonjs/sdk/core/heritage.js:145:23
spawn@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/commonjs/sdk/system/child_process.js:153:10
this.run@chrome://komodo/content/sdk/shell.js:170:23
runSh@chrome://state/content/js/sdk/tool.js:310:20
this.scripts@chrome://state/content/js/sdk/tool.js:498:9
getScripts@chrome://state/content/js/button.js:282:13
xtk.domutils.fireEvent@chrome://xtk/content/domutils.js:157:5
– EXCEPTION END –
[2022-03-15 13:59:40,930] [ERROR] console-logger: community.komodoide.com:443 uses an invalid security certificate.

The certificate is not trusted because the issuer certificate has expired.

(Error code: sec_error_expired_issuer_certificate)
(0) in :0
Traceback (most recent call last):
File “”, line 0, in

[2022-03-15 13:59:40,930] [DEBUG] ko.launch: Response: https://community.komodoide.com/changelog/120 (0)
[2022-03-15 13:59:41,220] [DEBUG] codeintel/process: stdout:
port:62852

pid:44464

[2022-03-15 13:59:41,220] [INFO] codeintel/process: CodeIntel started on port 62852
[2022-03-15 13:59:41,220] [DEBUG] codeintel/process: Calling callbacks for: started, number: 1
[2022-03-15 13:59:41,453] [WARNING] console-logger: Unknown descriptor ‘font-display’ in @font-face rule. Skipped to next declaration. (1) in less://komodo/skin/global/global.less:1429
[2022-03-15 13:59:51,200] [WARNING] console-logger: Unknown descriptor ‘font-display’ in @font-face rule. Skipped to next declaration. (1) in less://komodo/skin/global/global.less:1429

careyh · March 16, 2022, 4:14pm

@wblake, do you get the same error if you run the script from a CMD window? ie. state run activationMessage?

Maybe the state tool requires that the language be set in the script yaml, so language: perl under the appropriate script definition.

wblake · March 16, 2022, 6:27pm

Same message happens from the state run activationMessage. The acivationMessage script appears to have Perl set as its language.

careyh · March 17, 2022, 5:43pm

You got me on this one. I really don’t know why the state tool would be failing here. I think I have to pass you back to the Latest State Tool topics - ActiveState Community

Please do post back here when you get an answer though.

wblake · March 17, 2022, 8:15pm

careyh,
Thanks again. I will post the issue on the State Tool Topics.
Komodo almost never successfully runs the activestate.yaml downloaded by running state activate from cmd.exe and then invoking ko.
Interestingly If I create a “brand new” Komodo project and specify the Perl language, the resulting komodo-state tool project uses Perl 28.

As on a prior thread, I’m going to first uninstall and re-install Komodo (hopefully to discard pollution I introduced) and also try to use Komodo and the State Tool in a Linux environment to see if preferences like paths and language settings work more predictably.
Your patience with the newbie questions and dedication to the Komodo product remain most appreciated.

Regards,
Wil B

wblake · April 6, 2022, 2:13pm

FYI.
Just starting Komodo and State Tool under Windows 11 Windows Subsystem for Linux (WSL) Ubuntu and things work reasonably well so far.
The activestate.yaml error did not occur. The Activation Message script complained about a missing xterm - a WSL issue.

The current perl script project ran as expected, with Parallel::ForkManager working better in the Linux environment.

Some cleanup of the Workspace ought to occur along with finding the way to configure and enable xterm and perhaps Remote Perl Debug.

careyh · April 6, 2022, 3:47pm

@wblake, that is GREAT news. So you’ve switched to a WSL terminal instead of a Command Prompt window? That should work great.

wblake · April 7, 2022, 12:51pm

For now Windows Komodo Remote Debugging of the WSL Ubuntu Perl Project seems better than running Ubuntu Komodo under WSL. I have to review Komodo Windows path formats for access to directories and files on the WSL Linux file system. (WSL2 Komodo appeared to have issues with the WSLg window manager like the “hamburger menu” not working and the missing xterm error for state run script from the State Tool Integration menu. )

wblake · May 18, 2022, 5:15pm

Accessing the WSL2 Ubuntu files works as expected. Komodo for Linux Toolbar Main Menu does not work for me under WSL2 Ubuntu 20.04 . For now the Windows Komodo works good enough to edit the Linux files and proceed with remote Debugging.