hc icon indicating copy to clipboard operation
hc copied to clipboard

failing npm run start:http:template

Open avlo opened this issue 5 years ago • 0 comments

Hello. Trying to get HCVoting.sol contract deployed. Per README instructions, i'm using command:

npm run start:http:template

which doesn't appear to be working as described in the using HTTP section of the README. I'm seeing:

~/git/hc/holo-nick(master)$ npm run start:http:template
npm ERR! missing script: start:http:template

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/nick/.npm/_logs/2020-07-12T00_24_18_504Z-debug.log

and contents of /home/nick/.npm/_logs/2020-07-12T00_24_18_504Z-debug.log containing:

~/git/hc/holo-nick(master)$ cat /home/nick/.npm/_logs/2020-07-12T00_17_58_964Z-debug.log
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli   '/home/nick/.nvm/versions/node/v12.18.1/bin/node',
1 verbose cli   '/home/nick/.nvm/versions/node/v12.18.1/bin/npm',
1 verbose cli   'run',
1 verbose cli   'start:http:template'
1 verbose cli ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [
4 verbose run-script   'prestart:http:template',
4 verbose run-script   'start:http:template',
4 verbose run-script   'poststart:http:template'
4 verbose run-script ]
5 info lifecycle [email protected]~prestart:http:template: [email protected]
6 info lifecycle [email protected]~start:http:template: [email protected]
7 verbose lifecycle [email protected]~start:http:template: unsafe-perm in lifecycle true
8 verbose lifecycle [email protected]~start:http:template: PATH: /home/nick/.nvm/versions/node/v12.18.1/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/nick/git/hc/node_modules/.bin:/home/nick/.nvm/versions/node/v12.18.1/bin:/home/nick/.sdkman/candidates/gradle/current/bin:/home/nick/.local/bin:/home/nick/apps/maven/apache-maven-3.6.1/bin:/home/nick/apps/java/jdk-9.0.4/bin:/home/nick/.pyenv/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
9 verbose lifecycle [email protected]~start:http:template: CWD: /home/nick/git/hc
10 silly lifecycle [email protected]~start:http:template: Args: [
10 silly lifecycle   '-c',
10 silly lifecycle   'npm run start:http -- --template Template --template-init @ARAGON_ENS'
10 silly lifecycle ]
11 silly lifecycle [email protected]~start:http:template: Returned: code: 1  signal: null
12 info lifecycle [email protected]~start:http:template: Failed to exec start:http:template script
13 verbose stack Error: [email protected] start:http:template: `npm run start:http -- --template Template --template-init @ARAGON_ENS`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (/home/nick/.nvm/versions/node/v12.18.1/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack     at EventEmitter.emit (events.js:315:20)
13 verbose stack     at ChildProcess.<anonymous> (/home/nick/.nvm/versions/node/v12.18.1/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (events.js:315:20)
13 verbose stack     at maybeClose (internal/child_process.js:1021:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
14 verbose pkgid [email protected]
15 verbose cwd /home/nick/git/hc
16 verbose Linux 5.3.0-62-generic
17 verbose argv "/home/nick/.nvm/versions/node/v12.18.1/bin/node" "/home/nick/.nvm/versions/node/v12.18.1/bin/npm" "run" "start:http:template"
18 verbose node v12.18.1
19 verbose npm  v6.14.6
20 error code ELIFECYCLE
21 error errno 1
22 error [email protected] start:http:template: `npm run start:http -- --template Template --template-init @ARAGON_ENS`
22 error Exit status 1
23 error Failed at the [email protected] start:http:template script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

Getting similar errors when using npm run start:http:template as well. Hoping you might be able to help.

Incidentally, the npm run start:app command didn't work either. I had to modify it to be npm run start, but that did manage to get the http server started after updating truffle.js to contain:

const TruffleConfig = require('@aragon/os/truffle-config')

module.exports = {
  TruffleConfig, 
  compilers: {
    solc: {
      version: "^0.4.24",
      optimizer: {
        enabled: true,
        runs: 1 
      }
    }
  },
  networks: {
    development: {
      host: "127.0.0.1",
      port: 7545,
      gas: 400000,
      network_id: "*" // Match any network id
    }
  }
};

avlo avatar Jul 12 '20 00:07 avlo