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
[suggestion] Better error reporting on the client side. #4890
Comments
I also suffer from this. |
@sanjo Interesting. It seems to have a stack trace only sometimes: |
When I use the starter app ( And use my reproduce trigger code: if (Meteor.isClient) {
Tracker.autorun(function () {
if (Session.get('throw')) {
Cards.foo();
}
});
} And trigger it with Exception from Tracker recompute function: debug.js:41
ReferenceError: Cards is not defined
at stack-trace-autorun.js?087898c695bca84a46fc4ec3a4cad37d8878b275:5
at Tracker.Computation._compute (tracker.js:294)
at Tracker.Computation._recompute (tracker.js:313)
at Object.Tracker._runFlush (tracker.js:452)
at onGlobalMessage (setimmediate.js:102) I use Google Chrome 44. So still no reproduce :/ |
I think it needs to be in the context of using Blaze. I'll see what I can do. |
Yeah we definitely would need a reproduction to fix this. @trusktr when does it happen for you? Can you post an app where it happens here? |
I found that can reproduce it with some older version of Meteor and packages. I'm trying to reproduce same issue with new application with same packages (but never versions), no 'luck' so far. |
Issue is meteorhacks:kadira package _debug function overwrite. It removes stack trace, leaving only error message. Related bug is meteorhacks/kadira#193 Reproduced here https://github.com/Firfi/meteor-tracker-kadira-bug-reproduction |
It is fixed in Kadira. |
@Firfi thanks for checking that out! Any luck reproducing it without kadira? |
No luck reproducing it without. |
OK I see no reproductions after 3 people tried, going to close it then. |
I see errors like this which are a pain to track:
Errors of this form, from Tracker afterFlush, are always from line "debug.js:41", which is completely not helpful.
In the meantime, I'll keep laboriously hunting and hunting for the source of the error.
The text was updated successfully, but these errors were encountered: