Closed nygma2004 closed 4 years ago
I have been working too long in sane languages expecting that try/catch to actually, ya know, catch the errors....
Publishing with a new version with an ugly nuclear option fix for this. Ill have some others review and probably push a better version of this later once they tell me how bad I suck at node.js 😄
I just pushed 2.0 which I completely reworked to use promises around the library that gives castv2 support so that the error handling isn't abysmal. Try this out and let me know if it fixes your issue. It seemed to work better for me after I was able to eventually duplicate your issue.
Let me say in the beginning, I am not sure if I read the logs correctly. My node-red restarts about once a day recently, and looking at the syslog I see the following:
The logs looks the same from a few days ago when I was node-red restarted as well. I am running castv2 version 1.1.4 I am just upgrading to 1.1.7. Node Red version is 1.0.2.