Log function line numbers in Stitch errors
Marie Atterbury
Stitch logs can show an error message, for example:
Error:
{"message":"'replace' is not a function"}
There's also a link to the Stitch function that was running when the error was triggered.
With that said, there's no full stack trace, and no line number listed for the portion of code within the stitch function that triggered the error. It would be helpful to include this line number in future error logging to make debugging easier.
To share some context as an example, the error message above was caused by a Javascript
replace
method within the function, but this replace
method was used multiple times, and it was not apparent what logic was failing and returning the error.
Drew DiPalma
Hi Folks!
As part of our upcoming re-brand of "Stitch" to "Realm" we'll also be migrating our feedback forum and joining the rest of MongoDB at feedback.mongodb.com – as part of that transition, we'll be shutting down this forum. We're still keeping track of this feedback and all of the related comments/discussions, but have only migrated feedback with 5+ votes at this time. If you would like us to continue to track this item in the new forum please let us know.
M
Marc Blaesche
Please do consider this! Sometimes there are stack traces. But that is rarely and I cannot determine what factors lead to a stack trace. It is infuriatingly stupid to go looking through your functions to find the "forEach" that cannot be called on undefined. I have 19 forEach loops in my function chain. Which one is failing? I cannot tell because no line or function is given.
M
Marc Blaesche
It's been over a month now. Is there any update on this? It is really really hard to debug something that does not give lines to generic errors.