Hi.
In the good ol’ v3 days, I could throw an error in my JS codecs and it would be passed on, so when I would try and validate an object, I could see in the UI what was wrong.
All I get now is:
“Exception generated by quickjs”
And no further information.
Is there a way to make the JS codec error messages more verbose?
Thank you in advance 
This fix will be included in the next release:
My educated guess is that this should be fixing only uplink decoding. What about downlink encoding? 
This should fix the “truncated” errors in the API (and thus when using the enqueue API method):
Is there a release date for V4.6 known yet as debugging codec errors is quite hard without these fixes.
Released today.
Well - that is what I would call PERFECT timing
Well done and thank you, @brocaar & team. 
I am actually running 4.6.0 but I am only getting Exception generated by quickjs and nothing more. I’m running the docker version from the chirpstack/chirpstack:4.6.0 image. Do I need to pass an extra command line argument for more verbose error logs?
I’ve got the same issue. Is there something to configure?
I’m wondering it this is an issue of different verbosity of errors provided by otto and quickjs packages? Is it possible to make quickjs errors more verobse? Since debugging @ customer is now really difficult I am going to look into this and see what I can do
Have you tried the latest v4.8.1 release?
I have just tried and the current level of verbosity works for me! Thank you very much 
Now I only need to convince the customer to update their instance
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
