-
Notifications
You must be signed in to change notification settings - Fork 2k
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
uncaughtException masked #1438
Comments
Same issue on Ubuntu linux server. coffee test.coffee - No console.log, just normal strack trace output |
I just posted an answer to your StackOverflow question on this: This behavior is intentional—if the exception trickled all the way down to the process level, the So, you should compile to JS and re-run that JS every time it changes. You could write a Cakefile to do that (the most versatile option, but requires some legwork), or just use |
Why not enable this for Peeved, nothing personal but it just seems like the current workaround isn't a very good one unless I'm misunderstanding something. I want |
oddly enough, sometimes it seems to allow it, i'm confused... this case is broken and I've been able to verify as well... winstonjs/winston#47 |
I was just bitten by this as well. Exceptions thrown from the top level don't trigger uncaughtException, but they do if I wrap the throw in a setTimeout |
This causes problems with most server-side error handlers, such as Sentry. |
And bugsnag. |
Indeed. |
We're using coffee executable on the server. We're catching most of our errors with domain. Is this still an issue we should be aware about? We wanted to use bugsnag and their docs refer to this page. |
"We wanted to use bugsnag and their docs refer to this page" |
As we can see, CoffeeScript isn't for serious production deployments. |
I cant get this scrpt to work using the latest Node and latest CoffeeScript
Running coffee test.coffee just throws the normal stacktrace.
Howver the generated test.js (from coffee compile) works as planned with node test.generated.js
The text was updated successfully, but these errors were encountered: