Logger: unhandled runtime exceptions #756
Description
Please make sure you have searched for information in the following guides.
- Search the issues already opened: https://github.com/GoogleCloudPlatform/google-cloud-node/issues
- Search StackOverflow: http://stackoverflow.com/questions/tagged/google-cloud-platform+node.js
- Check our Troubleshooting guide: https://github.com/googleapis/google-cloud-node/blob/main/docs/troubleshooting.md
- Check our FAQ: https://github.com/googleapis/google-cloud-node/blob/main/docs/faq.md
- Check our libraries HOW-TO: https://github.com/googleapis/gax-nodejs/blob/main/client-libraries.md
- Check out our authentication guide: https://github.com/googleapis/google-auth-library-nodejs
- Check out handwritten samples for many of our APIs: https://github.com/GoogleCloudPlatform/nodejs-docs-samples
Link to the code that reproduces this issue. A link to a public Github Repository or gist with a minimal reproduction.
https://gist.github.com/bitekas/168ed8224104fb9d6a073efdddb122ff
A step-by-step description of how to reproduce the issue, based on the linked reproduction.
- Obtain verification result from google.androidpublisherv1
- Log the result using firebase logger.
- Observe the runtime exception
A clear and concise description of what the bug is, and what you expected to happen.
I expect the raw validation result to be reflected in the console so that I can copy the payload JSON and use it in the system unit tests.
Instead, the function terminates with an exception.
A clear and concise description WHY you expect this behavior, i.e., was it a recent change, there is documentation that points to this behavior, etc. **
The purpose of the logger is to report checkpoints and values in code so that they can be retrospected. The objects may be quite complex, including proxies, generators, recursive links, and so on.
The logger is suppsed to work in a predictable and controllable way (without trowing exceptions).