-
Notifications
You must be signed in to change notification settings - Fork 30k
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
deps: update v8_inspector #7796
Conversation
@rvagg As this includes a new License file Not sure if this is normally done during or after landing a PR... Ref; #7123 (comment) |
I think it could easily be included in this PR as a separate commit |
LGTM but can you break up the long line in node.gyp? GYP supports C-style string concatenation so you can just continue on the next line. Also, is there a reason the jinja test suite is included? Doesn't seem very necessary. |
# v8_inspector | ||
addlicense "v8_inspector" "deps/v8_inspector/third_party/v8_inspector" \ | ||
"$(cat ${rootdir}/deps/v8_inspector/third_party/v8_inspector/LICENSE)" | ||
# Build tooling for v8_inspector |
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.
@rvagg Is the ordering here important? Should the inspector be above the build/test tools?
I have updated @bnoordhuis fixed long line in
No strong reason other than minimizing the number of local changes to a vendored dependency in order to minimize the work if the dependency needs to be updated in the future. Is there a particular reason why the jinja test files should be locally deleted? EDIT: New CI: https://ci.nodejs.org/job/node-test-pull-request/3361/ |
The failures in the CI look like infrastructure / flakes. Will land tomorrow. |
Do they end up in release tarballs? If yes, they should either be deleted from the tree or the |
@ofrobots it sounds like an |
Removed tests from jinja2. New CI: https://ci.nodejs.org/job/node-test-pull-request/3401/.
The next time I have to do this, I will definitely consider writing a |
Will probably want to re-run CI after #7873 lands (hopefully within the hour). That will fix the bad build on four of the Linux hosts. |
Reran twice: https://ci.nodejs.org/job/node-test-pull-request/3408/, https://ci.nodejs.org/job/node-test-pull-request/3410/. windows-fanned builds seems to timeout after 30 minutes. The rest is looking green. |
One last time hoping the Windows stuff has passed: https://ci.nodejs.org/job/node-test-pull-request/3412/ |
That one failed too. Seems like the windows-fanned builds have infra issues. I will land this PR tomorrow morning. |
One more build after a rebase: https://ci.nodejs.org/job/node-test-pull-request/3424/. |
All green!!1! However, I noticed that the update licenses commit was added after the LGTM from @bnoordhuis . Can I get some LGTMs before landing? |
Lgtm |
Still LGTM. |
To add a LICENSE file along with the v8_inspector code, we need to pick up v8_inspector from an intermediate repository: https://github.com/pavelfeldman/v8_inspector. This repo still tracks upstream code in Blink. This roll also picks up the latest v8_inspector from upstream fixing a few issues. * Pickup commit id bc60957 from pavelfeldman/v8_inspector * Update node.gyp to adapt to the new file paths * Update the DevTools hash for the devtools frontend. Fixes: nodejs#7123 Fixes: nodejs#7736 Fixes: nodejs#7734 PR-URL: nodejs#7796 Reviewed-By: bnoordhuis - Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: jasnell - James M Snell <jasnell@gmail.com>
jinja.el is not shipped as part of the distribution, and neither is it used in the build. While not strictly necessary, removing it simplifies life from a licensing point of view. PR-URL: nodejs#7796 Reviewed-By: bnoordhuis - Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: jasnell - James M Snell <jasnell@gmail.com>
Start including the license from v8_inspector and its build time dependencies: jinja2 and markupsafe. PR-URL: nodejs#7796 Reviewed-By: bnoordhuis - Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: jasnell - James M Snell <jasnell@gmail.com>
Created using `tools/license-builder.sh`. PR-URL: nodejs#7796 Reviewed-By: bnoordhuis - Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: jasnell - James M Snell <jasnell@gmail.com>
PR-URL: nodejs#7796 Reviewed-By: bnoordhuis - Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: jasnell - James M Snell <jasnell@gmail.com>
Thanks. Landed as ea725ed...2554549. |
@ofrobots could you backport this to v6.x. It applies cleanly, but causes compile errors. |
@cjihrig I will take a look. |
To add a LICENSE file along with the v8_inspector code, we need to pick up v8_inspector from an intermediate repository: https://github.com/pavelfeldman/v8_inspector. This repo still tracks upstream code in Blink. This roll also picks up the latest v8_inspector from upstream fixing a few issues. * Pickup commit id bc60957 from pavelfeldman/v8_inspector * Update node.gyp to adapt to the new file paths * Update the DevTools hash for the devtools frontend. Fixes: #7123 Fixes: #7736 Fixes: #7734 PR-URL: #7796 Reviewed-By: bnoordhuis - Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: jasnell - James M Snell <jasnell@gmail.com>
jinja.el is not shipped as part of the distribution, and neither is it used in the build. While not strictly necessary, removing it simplifies life from a licensing point of view. PR-URL: #7796 Reviewed-By: bnoordhuis - Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: jasnell - James M Snell <jasnell@gmail.com>
Start including the license from v8_inspector and its build time dependencies: jinja2 and markupsafe. PR-URL: #7796 Reviewed-By: bnoordhuis - Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: jasnell - James M Snell <jasnell@gmail.com>
Created using `tools/license-builder.sh`. PR-URL: #7796 Reviewed-By: bnoordhuis - Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: jasnell - James M Snell <jasnell@gmail.com>
PR-URL: #7796 Reviewed-By: bnoordhuis - Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: jasnell - James M Snell <jasnell@gmail.com>
Checklist
make -j4 test
(UNIX), orvcbuild test nosign
(Windows) passesAffected core subsystem(s)
deps:v8_inspector
Description of change
To add a LICENSE file along with the v8_inspector code, we need to
pick up v8_inspector from an intermediate repository:
https://github.com/pavelfeldman/v8_inspector. This repo still tracks
upstream code in Blink.
This roll also picks up the latest v8_inspector from upstream fixing
a few issues.
Fixes: #7123
Fixes: #7736
Fixes: #7734
EDIT: CI:
https://ci.nodejs.org/job/node-test-pull-request/3337/EDIT: CI: https://ci.nodejs.org/job/node-test-pull-request/3361/