Skip to content
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(driver): stringify protocol error messages #6302

Merged
merged 2 commits into from
Oct 17, 2018

Conversation

paulirish
Copy link
Member

This is an actual log from LR:

LHError: UNKNOWN_ERROR Unknown error encountered with message 'Protocol error (Tracing.start): [object Object]'

The true origin is most likely... (drumroll...)

Tracing is already started

Our best friend. 👨‍❤️‍👨


As to why this PR makes sense.. Well... I can't really explain why message here is sometimes an object (and otherwise a string)... but the log above seems to indicate that's precisely what's happening. Could be the flu shot making me crazy though. 🤷‍♂️

@devtools-bot
Copy link

Howdy chief! Appreciate you filing this bug. 👏

We think this is the same root issue as #1091. So, we'll automatically mark this as a duplicate. Thanks!
🤖 Beep beep boop.

@patrickhulce
Copy link
Collaborator

lol #crushedbydevtoolsbot

Copy link
Collaborator

@patrickhulce patrickhulce left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

WFM! should we stringify .data too?

Copy link
Member

@brendankenny brendankenny left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[lgtm Lgtm]

@paulirish paulirish merged commit c92142f into master Oct 17, 2018
@paulirish paulirish deleted the stringifyerrormessage branch October 17, 2018 20:10
paulirish added a commit that referenced this pull request Oct 17, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants