-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
core(lantern): drop node id from error message #6774
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
WFM 👍
Yeah a repro case of this would be awesome :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is the id ever helpful when debugging? If not, seems fine to drop it. If so, maybe make an LHError and stick it on a property?
It isn't as an isolated aggregate error message. It's really useful when you're logging other parts of the graph too like I was when working on lantern and can look at the nodes to see which it is, but at that point, could just add back in a log statement. Might be nice to have some extra use of |
@@ -209,7 +209,7 @@ class BaseNode { | |||
} | |||
}); | |||
|
|||
if (!idToNodeMap.has(this.id)) throw new Error(`Cloned graph missing node ${this.id}`); | |||
if (!idToNodeMap.has(this.id)) throw new Error(`Cloned graph missing node`); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
smallest nit in the world of nits....BACKTICK
-> COMMA TO THE TOP
since there's no more interpolation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oops. I figured that edit would show up as a suggestion. I just changed it for you :)
In LR we collect and report all our errors. This one causes our metrics to get a little funky since it changes every time.
Does this work for you, @patrickhulce.
Also i imagine you want a few URLs that can reproduce this?
b/120845363