Truffle/npm error "Expected parameter 'from' not passed to function" - blockchain

I am playing with Truffle and while building, I am getting the following error. I searched internet but found nothing useful.
While running the "truffle.cmd deploy" command.
C:\Users\user_name\AppData\Roaming\npm\node_modules\truffle\build\webpack:\~\truffle-expect\index.js:3
expected_keys.forEach(function(key) { ^ Error: Expected parameter 'from' not passed to function.
at C:\Users\user_name\AppData\Roaming\npm\node_modules\truffle\build\webpack:\~\truffle-expect\index.js:5:1
at Array.forEach ()
at Object.options (C:\Users\user_name\AppData\Roaming\npm\node_modules\truffle\build\webpack:\~\truffle-expect\index.js:3:1)
at Object.run (C:\Users\user_name\AppData\Roaming\npm\node_modules\truffle\build\webpack:\~\truffle-migrate\index.js:122:1)
at C:\Users\user_name\AppData\Roaming\npm\node_modules\truffle\build\webpack:\~\truffle-core\lib\commands\migrate.js:79:1
at C:\Users\user_name\AppData\Roaming\npm\node_modules\truffle\build\webpack:\~\truffle-migrate\index.js:291:1
at C:\Users\user_name\AppData\Roaming\npm\node_modules\truffle\build\webpack:\~\truffle-migrate\index.js:115:1
at done (C:\Users\user_name\AppData\Roaming\npm\node_modules\truffle\build\webpack:\~\truffle-migrate\~\node-dir\lib\paths.js:61:1)
at C:\Users\user_name\AppData\Roaming\npm\node_modules\truffle\build\webpack:\~\truffle-migrate\~\node-dir\lib\paths.js:118:1
at FSReqWrap.oncomplete (fs.js:153:5) npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! tip-and-win#1.0.0 start: start cmd /K
ganache-cli --deterministic && truffle.cmd deploy && cd app && npm
install && npm run start npm ERR! Exit status 1 npm ERR! npm ERR!
Failed at the tip-and-win#1.0.0 start script. npm ERR! This is
probably not a problem with npm. There is likely additional logging
output above. npm WARN Local package.json exists, but node_modules
missing, did you mean to install?

Your current provider did not have any account. so, first you need to create an account on your rpc network by personal.newAccount(); after that run truffle migrate.
Hope this will help you to resolve this issue.

Related

Not able to create a new ember app - Could not resolve dependency error

I'm just trying to create a new app from scratch, but getting this error:
Command failed with exit code 1: npm install --loglevel error
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: ember-sample#0.0.0
npm ERR! Found: ember-cli#4.3.0
npm ERR! node_modules/ember-cli
npm ERR! dev ember-cli#"~4.3.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer ember-cli#"~3.2.0" from ember-cli-dependency-checker#3.3.0
npm ERR! node_modules/ember-cli-dependency-checker
npm ERR! dev ember-cli-dependency-checker#"^3.2.0" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
These are the repro steps:
open command prompt in Win11.
install ember
npm install -g ember-cli
create app ember-sample
ember new ember-sample
and just after that I get the error above.
Could I be missing anything? I have already installed node v16.14.2, npm 8.5.0, ember-cli: 4.3.0
I was already taking a look on ember.js official website
Actually Ember CLI is Compatible with NodeVersion 12. You might be using a later node versio like 14 or 16. My problem is solved when I downgraded to Node 12 lts
A fix is on its way. You could follow what #NullVoxPopuli said in the comments.
https://github.com/quaertym/ember-cli-dependency-checker/issues/132

Bodyparser breaking fresh installation of adonis 4.1

mygame#4.1.0 start /usr/src/app
node server.js
Error: Cannot find module '#adonisjs/bodyparser/providers/BodyParserProvider'
Require stack:
/usr/src/app/node_modules/require-stack/src/index.js
/usr/src/app/node_modules/require-stack/index.js
/usr/src/app/node_modules/#adonisjs/fold/src/Ioc/index.js
/usr/src/app/node_modules/#adonisjs/fold/index.js
/usr/src/app/server.js
1 requireStack
/usr/src/app/node_modules/require-stack/src/index.js:44
2 anonymous
/usr/src/app/node_modules/#adonisjs/fold/src/Registrar/index.js:104
3 arrayMap
/usr/src/app/node_modules/lodash/lodash.js:653
4 Function.map
/usr/src/app/node_modules/lodash/lodash.js:9622
5 interceptor
/usr/src/app/node_modules/lodash/lodash.js:17094
6 thru
/usr/src/app/node_modules/lodash/lodash.js:8859
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! mygame#4.1.0 start: node server.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the mygame#4.1.0 start 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/node/.npm/_logs/2021-03-25T00_06_01_885Z-debug.log
The problem is npm is installing the wrong version from body-parser, due to a recent push.
As a workaround:
go to package.json
you can replace the ^ with ~
"#adonisjs/bodyparser": "~2.0.9",
Since we prefixed the version with ~, NPM retrieved the latest patch version under the 2.0.9 minor version, which turned out to be 2.0.9 itself
For more info: https://github.com/adonisjs/bodyparser/issues/43

Build failing while deploying Perishable network on IBM cloud Blockchain starter plan

nvm_tree_contains_path /home/pipeline/.nvm /home/pipeline/.nvm/versions/node/v8.15.1
'[' -n 'Now using node v8.15.1 (npm v6.4.1)' ']'
nvm_echo 'Now using node v8.15.1 (npm v6.4.1)'
command printf '%s\n' 'Now using node v8.15.1 (npm v6.4.1)'
node -v
Now using node v8.15.1 (npm v6.4.1)
npm -v
v8.15.1
6.4.1
test_contracts
for CONTRACT in '${CONTRACTS}'
test_contract iot-blockchain-perishable-network
CONTRACT=iot-blockchain-perishable-network
'[' -f contracts/iot-blockchain-perishable-network/package.json ']'
test_composer_contract iot-blockchain-perishable-network
CONTRACT=iot-blockchain-perishable-network
echo testing composer contract iot-blockchain-perishable-network
pushd contracts/iot-blockchain-perishable-network
npm test
testing composer contract iot-blockchain-perishable-network
~/bc70ab6b-afeb-4ddf-a8ee-ddb7b7e23ce1/contracts/iot-blockchain-perishable-network ~/bc70ab6b-afeb-4ddf-a8ee-ddb7b7e23ce1
perishable-network#0.2.6-deploy.2 pretest /home/pipeline/bc70ab6b-afeb-4ddf-a8ee-ddb7b7e23ce1/contracts/iot-blockchain-perishable-network
npm run lint
perishable-network#0.2.6-deploy.2 lint /home/pipeline/bc70ab6b-afeb-4ddf-a8ee-ddb7b7e23ce1/contracts/iot-blockchain-perishable-network
eslint .
sh: 1: eslint: not found
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! perishable-network#0.2.6-deploy.2 lint: eslint .
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the perishable-network#0.2.6-deploy.2 lint script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?
npm ERR! A complete log of this run can be found in:
npm ERR! /home/pipeline/.npm/_logs/2019-03-06T14_37_44_449Z-debug.log
npm ERR! Test failed. See above for more details.
Finished: FAILED
You will just need to run npm install and see if everything was successfully installed. Because the project will run inside IBM Blockchain, you dont need to run it locally.
For a more detailed information on how to achieve your gold, check this answer:
https://stackoverflow.com/a/55358606/7004017

Elastic Beanstalk EBS NPM Bower install is failing

Having an issue with my EBS deployment. Getting this output everytime it tries to deploy the build.
Application deployment failed at 2018-07-02T02:46:14Z with exit status 1 and error: command npm_install_bower in .ebextensions/bower.config failed.
npm http GET https://registry.npmjs.org/bower
npm http GET https://registry.npmjs.org/bower
npm http GET https://registry.npmjs.org/bower
npm ERR! Error: UNABLE_TO_GET_ISSUER_CERT_LOCALLY
npm ERR! at SecurePair.<anonymous> (tls.js:1430:32)
npm ERR! at SecurePair.emit (events.js:92:17)
npm ERR! at SecurePair.maybeInitFinished (tls.js:1029:10)
npm ERR! at CleartextStream.read [as _read] (tls.js:521:13)
npm ERR! at CleartextStream.Readable.read (_stream_readable.js:341:10)
npm ERR! at EncryptedStream.write [as _write] (tls.js:418:25)
npm ERR! at doWrite (_stream_writable.js:226:10)
npm ERR! at writeOrBuffer (_stream_writable.js:216:5)
npm ERR! at EncryptedStream.Writable.write (_stream_writable.js:183:11)
npm ERR! at write (_stream_readable.js:602:24)
npm ERR! If you need help, you may report this log at:
npm ERR! <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR! <npm-#googlegroups.com>
npm ERR! System Linux 4.14.47-56.37.amzn1.x86_64
npm ERR! command "node" "/usr/bin/npm" "install" "-g" "bower"
npm ERR! cwd /opt/elasticbeanstalk/eb_infra
npm ERR! node -v v0.10.48
npm ERR! npm -v 1.3.6
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /opt/elasticbeanstalk/eb_infra/npm-debug.log
npm ERR! not ok code 0.
bower.config file is:
commands:
get_sudo:
command: echo Defaults:root \!requiretty >> /etc/sudoers
npm_install:
command: sudo yum -y --enablerepo=epel install nodejs npm
npm_install_bower:
command: sudo npm install -g bower
container_commands:
01_bower_install:
command: "export PATH=$PATH; $NODE_HOME/bin/node ./node_modules/bowe/bin/bower -V install --allow-root -F > /tmp/01_bower_install.log"
Tried it without 01_bower_install part as well but same result. Fails to deploy. Was working fine until 2 days ago on the instance and now showing:
Forbidden You don't have permission to access / on this server.
..on the URL.
Help greatly appreciated!
I spent few hours today on the same issue, bower would not be installed by npm and would not run. Eventually got it work as follows:
1) remove "bower" from package.json
2) here is my ebextension file that managed to install bower and run it, by making it a global command:
container_commands:
install_bower:
command: "export PATH=$PATH:$NODE_HOME/bin; npm install bower -g; bower install --allow-root"
Cheers,
Z.

Zurb Foundation For Emails gulp --production Fails

I've been using Zurb Foundation for Emails successfully for quite some time. Suddenly the build process is failing.
I updated to Node 7.7.2 and NPM 4.1.2, deleted the node_modules directory and ran npm install to reinstall the dependencies, but it didn't solve the issue.
$ npm run build
foundation-emails-template#1.0.0 build /Users/[REDACTED]
gulp --production
[12:46:56] Requiring external module babel-register
[12:46:57] Using gulpfile ~/[REDACTED]/gulpfile.babel.js
[12:46:57] Starting 'default'...
[12:46:57] Starting 'build'...
[12:46:57] Starting 'clean'...
[12:46:57] Finished 'clean' after 11 ms
[12:46:57] Starting 'pages'...
[12:46:59] Finished 'pages' after 1.32 s
[12:46:59] Starting 'sass'...
[12:47:05] 'sass' errored after 6.91 s
[12:47:05] Error in plugin 'gulp-uncss'
Message:
Unexpected EOF
Details:
domainEmitter: [object Object]
domain: [object Object]
domainThrown: false
[12:47:05] 'build' errored after 8.25 s
[12:47:05] 'default' errored after 8.25 s
npm ERR! Darwin 15.6.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "build"
npm ERR! node v7.7.2
npm ERR! npm v4.1.2
npm ERR! code ELIFECYCLE
npm ERR! foundation-emails-template#1.0.0 build: `gulp --production`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the foundation-emails-template#1.0.0 build script 'gulp --production'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the foundation-emails-template package,
npm ERR! not with npm itself.
Or if I try to run gulp --production by itself:
$ gulp --production
[12:29:38] Requiring external module babel-core/register
[12:29:39] Using gulpfile ~/[REDACTED]/gulpfile.babel.js
/usr/local/lib/node_modules/gulp/bin/gulp.js:129
gulpInst.start.apply(gulpInst, toRun);
^
TypeError: Cannot read property 'apply' of undefined
at /usr/local/lib/node_modules/gulp/bin/gulp.js:129:19
at _combinedTickCallback (internal/process/next_tick.js:73:7)
at process._tickDomainCallback (internal/process/next_tick.js:128:9)
npm start works as expected; I just can't inline the styles.
Any ideas? TIA.
It's because the node environment had changed.
Run this in your console:
npm rebuild node-sass
npm rebuild gulp-uncss
It should fix the issue.
I got the same error and was caused by a code-specific issue so make sure all your code is valid. In my case I was missing a closing " on a class.