★ wanayoo — archive 1999 https://github.com/nodejs/node/pull/22529Nouvelle recherche | Portail wanayoo
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

src: fix NODE_OPTIONS parsing bug #22529

Closed
wants to merge 1 commit into from

Conversation

Projects
None yet
9 participants
@addaleax
Copy link
Member

addaleax commented Aug 26, 2018

I, uhm, might have messed up by using a substr(start, end) signature when std::string actually uses substr(start, len). Fix that.

Fixes: #22526
Refs: #22392

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • commit message follows commit guidelines
src: fix NODE_OPTIONS parsing bug
I, uhm, might have messed up by using a `substr(start, end)`
signature when `std::string` actually uses `substr(start, len)`.
Fix that.

Fixes: #22526
Refs: #22392
@addaleax

This comment has been minimized.

Copy link
Member Author

addaleax commented Aug 26, 2018

CI: https://ci.nodejs.org/job/node-test-pull-request/16754/

I have labeled this fast-track, mostly because this isn’t a complex change by itself and it would be important that this goes into the same release as #22392 (and I think we may want to do a v10.x this week). Feel free to 👍 or 👎 this comment depending on your opinion on that.

@BridgeAR
Copy link
Member

BridgeAR left a comment

LGTM. Thanks for the quick fix.

@@ -29,6 +31,9 @@ expect('--v8-pool-size=10', 'B\n');
expect('--trace-event-categories node', 'B\n');
// eslint-disable-next-line no-template-curly-in-string
expect('--trace-event-file-pattern {pid}-${rotation}.trace_events', 'B\n');
// eslint-disable-next-line no-template-curly-in-string
expect('--trace-event-file-pattern {pid}-${rotation}.trace_events ' +

This comment has been minimized.

@mscdex

mscdex Aug 26, 2018

Contributor

Is it possible we could avoid hard-coding all of these options somehow with 22490 or would that require too much node options metadata to know what (if any) arguments to pass for each?

This comment has been minimized.

@addaleax

addaleax Aug 26, 2018

Author Member

I think it would work for a number of options (mostly the simple boolean ones), but there are quite a few that change output in some way…

@refack

refack approved these changes Aug 26, 2018

@refack

This comment has been minimized.

Copy link
Member

refack commented Aug 26, 2018

Simple fixes for regressions, should be fast tracked.

Resume CI:https://ci.nodejs.org/job/node-test-commit/20911/

@Trott

This comment has been minimized.

@targos

This comment has been minimized.

Copy link
Member

targos commented Aug 26, 2018

@addaleax

This comment has been minimized.

Copy link
Member Author

addaleax commented Aug 26, 2018

Landed in 1c05b16

@addaleax addaleax closed this Aug 26, 2018

@addaleax addaleax deleted the addaleax:fix-node-options branch Aug 26, 2018

addaleax added a commit that referenced this pull request Aug 26, 2018

src: fix NODE_OPTIONS parsing bug
I, uhm, might have messed up by using a `substr(start, end)`
signature when `std::string` actually uses `substr(start, len)`.
Fix that.

Fixes: #22526
Refs: #22392

PR-URL: #22529
Reviewed-By: Gus Caplan <me@gus.host>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: Refael Ackermann <refack@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>

addaleax added a commit that referenced this pull request Aug 28, 2018

src: fix NODE_OPTIONS parsing bug
I, uhm, might have messed up by using a `substr(start, end)`
signature when `std::string` actually uses `substr(start, len)`.
Fix that.

Fixes: #22526
Refs: #22392

PR-URL: #22529
Reviewed-By: Gus Caplan <me@gus.host>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: Refael Ackermann <refack@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>

targos added a commit that referenced this pull request Sep 3, 2018

src: fix NODE_OPTIONS parsing bug
I, uhm, might have messed up by using a `substr(start, end)`
signature when `std::string` actually uses `substr(start, len)`.
Fix that.

Fixes: #22526
Refs: #22392

PR-URL: #22529
Reviewed-By: Gus Caplan <me@gus.host>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: Refael Ackermann <refack@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>

@targos targos referenced this pull request Sep 5, 2018

Merged

Release proposal: v10.10.0 #22716

targos added a commit that referenced this pull request Sep 6, 2018

src: fix NODE_OPTIONS parsing bug
I, uhm, might have messed up by using a `substr(start, end)`
signature when `std::string` actually uses `substr(start, len)`.
Fix that.

Fixes: #22526
Refs: #22392

PR-URL: #22529
Reviewed-By: Gus Caplan <me@gus.host>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: Refael Ackermann <refack@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.