4 ms·
Why didn't you check the logs as the first thing to understand what's happening -- a standard operational practice? And then to prevent this, you just lock the
by lxe 3y ago
Why didn't you check the logs as the first thing to understand what's happening -- a standard operational practice?
And then to prevent this, you just lock the dependencies via a lockfile -- a well documented solution.
This is just another amateur "javascript bad" post.
- rezonant 3y agoAgreed, when they popped out this "such and such isn't a function" I lost the thread. You would know about that before you even started if you just read some logs. Unless they don't have logs, in which case a choice of language isn't going to solve their problems.
- fendy3002 3y agoOr not handling uncaughtException or unhandledPromiseRejection, which may be common mistakes.
- rezonant 3y agoHandling uncaughtException and unhandledPromiseRejection is a common mistake. You should not do it unless you have a good reason. Your program should die for science, and you should fix the place where you didn't handle that exception or rejection. Unless of course your handler results in dying for science, then it's fine (ie for sending to an observability service first)
- warkanlock 3y agodid you read the article in the first place? this didn't expose any exception and it just keep loading to eternity until timeout