How to interpret [server-internal] errors in kadira without any stacktrace

In Kadira I’m seeing a lot of server-internal errors without any info or stack trace. E.g. this one:

Are other people also seeing this and where could this originate from?

Did you ever figure this out?

This is from Meteor calling Meteor._debug without any arguments to show an empty line in the logs, after logging an error in a method or publisher.

This and many other unhelpful errors were improved in the latest version of It is compatible with all Meteor APMs based on Kadira.

1 Like

Thanks! Btw, I ran in this issue: which seems to have been fixed, but not yet released.