-
-
Notifications
You must be signed in to change notification settings - Fork 326
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
Upgrade Otto Javascript interpreter #664
Comments
@brocaar Any update on this, please? |
@hubpav please see https://forum.chirpstack.io/t/help-testing-chirpstack-v4-test-releases/13970. ChirpStack v4 contains a different JS runtime and will also include the NodeJS "Buffer" class (e.g. for base64 or hex encoding / decoding). I'm happy to review a PR to upgrade Otto for the current v3 version. |
@brocaar Oh, wow! Having the Node.js Buffer class available is a game-changer for us :) No point to upgrade v3 then. Thanks! P. |
Please note that the above test-releases do not include the Buffer class yet, I pushed this change literally two hours ago :-) (chirpstack/chirpstack@5b1d70c) |
@brocaar Alright - will wait for the next test release. BTW Is there an estimated milestone for the stable v4 release? |
Summary
Please, update Otto Javascript interpreter to the most recent version with the next ChirpStack AS release. Currently, the repo is locked against this commit:
https://github.com/robertkrimen/otto/tree/37f8e9a2460cc10ee975f900b11af0fc55ca1406
What is the use-case?
There have been numerous bug fixes in Otto since Dec 17, 2019. I came across expression evaluation incorrectness as compared to Node.js. Unfortunately, I did not have time to test against the most recent version of Otto's most recent commit, but given the number of bugs fixed in the meantime, the preemptive update to Chirpstack should be done anyway.
Thanks!
The text was updated successfully, but these errors were encountered: