Skip to content

Cannot use 'in' operator to search for '0' in arguments_marker #16781

Closed
Closed
Cannot use 'in' operator to search for '0' in arguments_marker#16781
Labels
wrong repoIssues that should be opened in another repository.

Description

@SheetJSDev
SheetJSDev
opened on Nov 5, 2017
  • Version: 9.0.0
  • Platform: darwin and linux

Error as stated in message.

To elicit the error, clone https://github.com/sheetjs/js-xlsx and npm install:

$ cd /tmp
$ git clone https://github.com/sheetjs/js-xlsx
$ cd js-xlsx
$ npm install -g npm@4.3.x
$ npm install

Relevant cut from the debug log:

1386 silly addNamed right-align@0.1.3
1387 verbose addNamed "0.1.3" is a plain semver version for right-align
1388 verbose get https://registry.npmjs.org/wordwrap not expired, no request
1389 silly cache afterAdd right-align@0.1.3
1390 verbose afterAdd /Users/sheetjs/.npm/right-align/0.1.3/package/package.json not in flight; writing
1391 verbose correctMkdir /Users/sheetjs/.npm correctMkdir not in flight; initializing
1392 silly cache afterAdd wordwrap@0.0.2
1393 verbose afterAdd /Users/sheetjs/.npm/wordwrap/0.0.2/package/package.json not in flight; writing
1394 verbose correctMkdir /Users/sheetjs/.npm correctMkdir not in flight; initializing
1395 verbose afterAdd /Users/sheetjs/.npm/wordwrap/0.0.2/package/package.json written
1396 verbose afterAdd /Users/sheetjs/.npm/right-align/0.1.3/package/package.json written
1397 verbose stack TypeError: Cannot use 'in' operator to search for '0' in arguments_marker
1397 verbose stack     at forEach (<anonymous>)
1397 verbose stack     at Entry._setProps (/usr/local/lib/node_modules/npm/node_modules/tar/lib/entry.js:165:25)
1397 verbose stack     at new Entry (/usr/local/lib/node_modules/npm/node_modules/tar/lib/entry.js:46:8)
1397 verbose stack     at Parse._startEntry (/usr/local/lib/node_modules/npm/node_modules/tar/lib/parse.js:241:11)
1397 verbose stack     at Parse._process (/usr/local/lib/node_modules/npm/node_modules/tar/lib/parse.js:131:12)
1397 verbose stack     at BlockStream.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/tar/lib/parse.js:47:8)
1397 verbose stack     at emitOne (events.js:125:13)
1397 verbose stack     at BlockStream.emit (events.js:221:7)
1397 verbose stack     at BlockStream._emitChunk (/usr/local/lib/node_modules/npm/node_modules/tar/node_modules/block-stream/block-stream.js:145:10)
1397 verbose stack     at BlockStream.write (/usr/local/lib/node_modules/npm/node_modules/tar/node_modules/block-stream/block-stream.js:45:10)

This is not triggered by any previous node version (tested against latest 8.x 7.x 6.x 5.x 4.x 0.12.x 0.10.x 0.8.x).

A quick search suggests this is possibly a v8 issue: https://bugs.chromium.org/p/chromium/issues/detail?id=777836

Activity

  1. mscdex commented on Nov 5, 2017

    @mscdex
    mscdex
    on Nov 5, 2017
    Contributor

    General help questions should be posted to the nodejs/help issue tracker instead. This issue tracker is for reporting bugs and submitting feature requests for node core. Issues with npm or other tools that use node should be posted to the appropriate issue tracker for those tools, unless it can be proven that the issue is in fact with node core and not the tool in question.

  2. mscdex
    closed this as completedon Nov 5, 2017
  3. mscdex
    added
    wrong repoIssues that should be opened in another repository.
    on Nov 5, 2017

  4. SheetJSDev commented on Nov 5, 2017

    @SheetJSDev
    SheetJSDev
    on Nov 5, 2017
    ContributorAuthor

    If you read the proposed fix in the linked issue from chromium:

    https://bugs.chromium.org/p/chromium/issues/detail?id=777836#c6

    https://chromium-review.googlesource.com/c/v8/v8/+/738176

    Disable --turbo-inline-array-builtins by default.

    Current chrome stable has a high number of crashes due to bugs in
    this feature. These bugs are already fixed but the fixes are hard
    to merge back. Therefore we decided to disable the feature in stable.
    This CL is intended to be merged to stable and then reverted in tot.

    The comment certainly suggests this is something related to V8. The issue itself happens to manifest in npm usage, but the actual problem is within the domain of node core.

  5. mscdex commented on Nov 5, 2017

    @mscdex
    mscdex
    on Nov 5, 2017
    Contributor

    See: #16704

  6. malept
    added a commit that references this issue on Nov 13, 2017

    CI: allow Node 9 to fail

    fb0575b

  7. DanielRuf commented on Feb 19, 2018

    @DanielRuf
    DanielRuf
    on Feb 19, 2018

    Is this also in Node.js 9 and in which versions?

  8. squaremo
    added a commit that references this issue on Jul 2, 2018

    Bump uglify version and tested NodeJS 9-series

    6410bc3
  9. squaremo
    added a commit that references this issue on Jul 9, 2018

    Bump uglify version and tested NodeJS 9-series

    55d08ba
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    wrong repoIssues that should be opened in another repository.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions