Skip to content

tools: roll inspector_protocol to f67ec5 - #26303

Merged
refack merged 1 commit into
nodejs:masterfrom
pavelfeldman:inspector_protocol
Mar 4, 2019
Merged

tools: roll inspector_protocol to f67ec5#26303
refack merged 1 commit into
nodejs:masterfrom
pavelfeldman:inspector_protocol

Conversation

@pavelfeldman

Copy link
Copy Markdown
Contributor

Fixes: #25808

@nodejs-github-botnodejs-github-bot added c++ Issues and PRs that require attention from people who are familiar with C++. lib / src Issues and PRs related to general changes in the lib or src directory. labels Feb 25, 2019
Comment threadsrc/inspector/node_string.cc Outdated

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

This should probably be

Suggested change
ProtocolMessage binaryToMessage(std::vector<uint8_t> message) {
ProtocolMessage binaryToMessage(conststd::vector<uint8_t>& message) {

?

Copy link
Copy Markdown
ContributorAuthor

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.

Comment threadsrc/inspector/node_string.h Outdated

Copy link
Copy Markdown
Member

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.

Copy link
Copy Markdown
ContributorAuthor

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.

Copy link
Copy Markdown
ContributorAuthor

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

@targos

Copy link
Copy Markdown
Member

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.

@pavelfeldman

Copy link
Copy Markdown
ContributorAuthor

Is there a guide/documentation on how to update this dependency?

we have scripts doing that in the v8 / chromium lands, let us add another one for Node.

@pavelfeldmanpavelfeldman changed the title Roll tools/inspector_protocol to f67ec5180f476830e839226b5ca948e43070…tools: roll inspector_protocol to f67ec5180f476830e839226b5ca948e43070…Feb 25, 2019
@pavelfeldmanpavelfeldman changed the title tools: roll inspector_protocol to f67ec5180f476830e839226b5ca948e43070…tools: roll inspector_protocol to f67ec5Feb 25, 2019

@refackrefack left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

RSLGTM

@refack

Copy link
Copy Markdown
Contributor

@pavelfeldman, thank you for the bump.
Could you have forgotten to add renamed files?

From Travis:

make[1]: *** No rule to make target `../tools/inspector_protocol/code_generator.py', needed by `26acdf201a53d5709754b88c308e871df22184f9.intermediate'. Stop.

@pavelfeldman

Copy link
Copy Markdown
ContributorAuthor

Turns out I lost all the added third party files while shuffling them between the repos :/ ...

@addaleax

Copy link
Copy Markdown
Member

@pavelfeldman What’s the status of this PR?

@targos

Copy link
Copy Markdown
Member

I think it's ready? I confirm this PR fixes the canary builds.

@refackrefack self-assigned this Mar 4, 2019
@refack

Copy link
Copy Markdown
Contributor

Fixes: nodejs#25808
PR-URL: nodejs#26303
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Refael Ackermann <refack@gmail.com>
@refack
refackforce-pushed the inspector_protocol branch from c5a8f91 to d775d74CompareMarch 4, 2019 16:48
@refack
refack merged commit d775d74 into nodejs:masterMar 4, 2019
@refackrefack removed their assignment Mar 11, 2019
BridgeAR pushed a commit to BridgeAR/node that referenced this pull request Mar 12, 2019
Fixes: nodejs#25808
PR-URL: nodejs#26303
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Refael Ackermann <refack@gmail.com>
BethGriggs pushed a commit that referenced this pull request Apr 16, 2019
Fixes: #25808
PR-URL: #26303
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Refael Ackermann <refack@gmail.com>
@BethGriggsBethGriggs mentioned this pull request May 1, 2019
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

c++Issues and PRs that require attention from people who are familiar with C++.lib / srcIssues and PRs related to general changes in the lib or src directory.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants

@pavelfeldman@targos@refack@addaleax@nodejs-github-bot