Closed shabiel closed 2 years ago
What is normal best practice in this case ? Does it record the error in the node.js system, or would it need to be changed to do that ? Dave
On Mon, Jun 6, 2022 at 8:08 AM Sam Habiel @.***> wrote:
LOGERR doesn't set the global that contains the error information and as a result, they are suppressed and never sent back to the client.
— Reply to this email directly, view it on GitHub https://github.com/shabiel/M-Web-Server/issues/50, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJPNTZY7GQINLPZJP6MX73VNXS5LANCNFSM5X7FWE3Q . You are receiving this because you are subscribed to this thread.Message ID: @.***>
Oh this is just a plain bug... we don't use NodeJS anywhere. No relation to it. We just need to report the error like we normally do.
Implemented in PR#52
When an M error happens during the execution of the Web Server,
LOGERR
doesn't set the global that contains the error information because we are running in "No Globals" mode; and as a result, they are suppressed and never sent back to the client.