-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[jsscripting] jsscripting automation bundle installation issues #11219
Comments
This issue has been mentioned on openHAB Community. There might be relevant details there: |
This issue has been mentioned on openHAB Community. There might be relevant details there: https://community.openhab.org/t/usage-of-new-ecma2021-automation-scripting-graalvm/122724/24 |
I believe that the bug is that it requires the This report includes the second part which has the error message: This is expected behaviour; if you want access to the item registry it must be imported, there are not magic predefined symbols like in the old runtime. |
The itemRegistry issue is discussed in #11221 |
@ssalonen |
I say we close this. Probably lack of mime type separation was problematic? Is the folder created now automatically? |
Yes, I guess. Combined with the difference between Nashorn and JS Scripting (Nashorn implicitly imports everything, JS Scripting needs explicit imports).
I am not sure, I’ll check later. |
I’ve just performed a fresh install of openHAB on one of my test systems, the folder is automatically created. |
I have observed errors with the jsscripting automation bundle installation.
Expected Behavior
/home/<RETRACTED>/src/openhab-tests/oh310-jsscripting-test/conf/automation/lib/javascript/personal
folder, or create it automatically.Current Behavior
Possible Solution
Steps to Reproduce (for Bugs)
Installation issues, steps to reproduce:
( runs without an error this time)
mkdir -p /home/<RETRACTED>/src/openhab-tests/oh310-jsscripting-test/conf/automation/lib/javascript/personal
(not restarting openHAB in between)Restart openHAB
Run oldscript (this time failing!)
newscript fails with same error.
(filing separate issue on this particular error -- the point is that now the error is different than before)
Context
Trying to migrate to ES6 in rules/scripts.
Your Environment
I can reproduce with 3.1.0 release and 3.2.0 M2.
The text was updated successfully, but these errors were encountered: