+1 I verified signature and checksums. I ran unit tests with Node.js 8.9.1 on Debian GNU/Linux sid. All tests were passed.
I used https://nodejs.org/dist/v8.9.1/node-v8.9.1-linux-x64.tar.xz . Thanks, -- kou In <[email protected]> "Re: [VOTE] Release Apache Arrow JavaScript 0.2.0 - RC1" on Wed, 29 Nov 2017 23:40:45 +0900 (JST), Kouhei Sutou <[email protected]> wrote: > Hi, > > I tried with Node.js 6.10.2 installed by package on Debian > GNU/Linux sid then I got the following error: > > -- > % npx run-s clean:all lint build > >> [email protected] clean:all /tmp/apache-arrow-js-0.2.0 >> run-p clean clean:testdata > > >> [email protected] clean /tmp/apache-arrow-js-0.2.0 >> gulp clean > > >> [email protected] clean:testdata /tmp/apache-arrow-js-0.2.0 >> gulp clean:testdata > > /tmp/apache-arrow-js-0.2.0/gulp/uglify-task.js:40 > const targetConfig = { ...commonConfig, > ^^^ > SyntaxError: Unexpected token ... > at createScript (vm.js:56:10) > at Object.runInThisContext (vm.js:97:10) > at Module._compile (module.js:542:28) > at Object.Module._extensions..js (module.js:579:10) > at Module.load (module.js:487:32) > at tryModuleLoad (module.js:446:12) > at Function.Module._load (module.js:438:3) > at Module.require (module.js:497:17) > at require (internal/module.js:20:19) > at Object.<anonymous> > (/tmp/apache-arrow-js-0.2.0/gulp/build-task.js:21:20) > /tmp/apache-arrow-js-0.2.0/gulp/uglify-task.js:40 > const targetConfig = { ...commonConfig, > ^^^ > SyntaxError: Unexpected token ... > at createScript (vm.js:56:10) > at Object.runInThisContext (vm.js:97:10) > at Module._compile (module.js:542:28) > at Object.Module._extensions..js (module.js:579:10) > at Module.load (module.js:487:32) > at tryModuleLoad (module.js:446:12) > at Function.Module._load (module.js:438:3) > at Module.require (module.js:497:17) > at require (internal/module.js:20:19) > at Object.<anonymous> > (/tmp/apache-arrow-js-0.2.0/gulp/build-task.js:21:20) > npm ERR! code ELIFECYCLE > npm npmERR! errno 1 > ERR! code ELIFECYCLE > npm ERR! errno 1 > npm ERR! [email protected] clean: `gulp clean` > npm ERR! Exit status 1 > npm ERR! > npm npmERR! ERR! Failed at the [email protected] clean script. > npm [email protected] clean:testdata: `gulp clean:testdata` > npm ERR!ERR! Exit status 1 > This is probably not a problem with npm. There is likely additional logging > output above. > npm ERR! > npm ERR! Failed at the [email protected] clean:testdata script. > npm ERR! This is probably not a problem with npm. There is likely additional > logging output above. > > > npmnpm ERR!ERR! A complete log of this run can be found in: > npm A complete log of this run can be found in: > ERR! /home/kou/.npm/_logs/2017-11-29T14_37_00_974Z-debug.log > npm ERR! /home/kou/.npm/_logs/2017-11-29T14_37_00_974Z-debug.log > ERROR: "clean" exited with 1. > npm ERR! code ELIFECYCLE > npm ERR! errno 1 > npm ERR! [email protected] clean:all: `run-p clean clean:testdata` > npm ERR! Exit status 1 > npm ERR! > npm ERR! Failed at the [email protected] clean:all script. > npm ERR! This is probably not a problem with npm. There is likely additional > logging output above. > > npm ERR! A complete log of this run can be found in: > npm ERR! /home/kou/.npm/_logs/2017-11-29T14_37_01_074Z-debug.log > ERROR: "clean:all" exited with 1. > -- > > It seems that I should use more recent Node.js. > > It may be better that we add "engines" entry to > package.json. > > https://docs.npmjs.com/files/package.json#engines > > > I'll try again with more recent Node.js later. > > > Thanks, > -- > kou > > In <CAJPUwMBJvhrpMjBiGLsg=j7o0cs6cxgt9hplcqudzagesqv...@mail.gmail.com> > "Re: [VOTE] Release Apache Arrow JavaScript 0.2.0 - RC1" on Tue, 28 Nov > 2017 14:49:26 -0500, > Wes McKinney <[email protected]> wrote: > >> Could folks take a look at this release? To get NodeJS and test the >> release, do the following: >> >> 1. Install nvm, and node >> >> curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.33.6/install.sh >> | bash >> nvm install node >> >> 2. Extract tarball, run unit tests: >> >> tar xvf apache-arrow-js-0.2.0.tar.gz >> cd apache-arrow-js-0.2.0/ >> >> npm install >> npx run-s clean:all lint build >> npm run test >> >> On Mon, Nov 27, 2017 at 12:02 PM, Wes McKinney <[email protected]> wrote: >>> +1 (binding) >>> >>> Ran dev/release/js-verify-release-candidate.sh >>> >>> Verified checksums, signature. RAT report looks OK. Ran unit tests >>> with NodeJS 9.2 (installed with nvm https://github.com/creationix/nvm) >>> >>> On Mon, Nov 27, 2017 at 10:45 AM, Wes McKinney <[email protected]> wrote: >>>> Hello all, >>>> >>>> I'd like to propose the 1st release candidate (rc1) of Apache >>>> Arrow JavaScript version 0.2.0. This is a first alpha release, >>>> made separately from the primary release line so that JavaScript >>>> can release more frequently. >>>> >>>> The source release rc1 is hosted at [1]. >>>> >>>> This release candidate is based on commit >>>> 61763504e53fb5531f1d642c399b8ec7b094b337 [2] >>>> >>>> Please download, verify checksums and signatures, run the unit tests, and >>>> vote >>>> on the release. The easiest way is to use the JavaScript-specific release >>>> verification script dev/release/js-verify-release-candidate.sh. >>>> >>>> The vote will be open for at least 24 hours and will close once >>>> enough PMCs have approved the release. >>>> >>>> [ ] +1 Release this as Apache Arrow JavaScript 0.2.0 >>>> [ ] +0 >>>> [ ] -1 Do not release this as Apache Arrow JavaScript 0.2.0 because... >>>> >>>> Thanks, >>>> Wes >>>> >>>> How to validate a release signature: >>>> https://httpd.apache.org/dev/verification.html >>>> >>>> [1]: >>>> https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-js-0.2.0-rc1/ >>>> [2]: >>>> https://github.com/apache/arrow/tree/61763504e53fb5531f1d642c399b8ec7b094b337
