-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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
tools: roll inspector_protocol to f67ec5 #26303
Conversation
return message; | ||
} | ||
|
||
ProtocolMessage binaryToMessage(std::vector<uint8_t> message) { |
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.
This should probably be
ProtocolMessage binaryToMessage(std::vector<uint8_t> message) { | |
ProtocolMessage binaryToMessage(const std::vector<uint8_t>& message) { |
?
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.
Not really, we are std::move
-ing binary messages around. It is likely that we switch to using std::unique_ptr<std::vector>
for clarity at some point.
src/inspector/node_string.h
Outdated
class Binary { | ||
public: | ||
const uint8_t* data() const { | ||
DCHECK(false); |
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.
Does it make sense to UNREACHABLE();
? You can drop the return
statements in that case.
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.
Ah, perfect, that's what it is in v8/chromium, I was not sure if node prefers that as well.
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.
Correction, it was UNIMPLEMENTED
in v8/chromium. Anyhow, using UNREACHABLE
now
Is there a guide/documentation on how to update this dependency? This PR removes more lines than it adds while my try here adds 7k. |
b180034
to
73d1e25
Compare
we have scripts doing that in the v8 / chromium lands, let us add another one for Node. |
73d1e25
to
9964706
Compare
9964706
to
f041207
Compare
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.
RSLGTM
@pavelfeldman, thank you for the bump. From Travis:
|
f041207
to
c5a8f91
Compare
Turns out I lost all the added third party files while shuffling them between the repos :/ ... |
@pavelfeldman What’s the status of this PR? |
I think it's ready? I confirm this PR fixes the canary builds. |
Fixes: nodejs#25808 PR-URL: nodejs#26303 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Refael Ackermann <[email protected]>
c5a8f91
to
d775d74
Compare
Fixes: nodejs#25808 PR-URL: nodejs#26303 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Refael Ackermann <[email protected]>
Fixes: #25808 PR-URL: #26303 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Refael Ackermann <[email protected]>
Fixes: #25808