#1703: fixing logger runtime exceptions #1704
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fixing the issue #1703.
Googleapis returns a proxy to an object with a missing "size" property due to an outdated node-fetch library, and this causes the logger to throw an exception. This PR fixes that.
Also improved lookup time to O(1), and fixed a potential bug for logging objects such as
{ toJSON: true }
: in the current implementationdebug({toJSON: true});
is throwing an exception. Pretty nasty given the amount of the Internet using this logger, and hard to triage. This is also fixed.Code sample