I'm running into a wall when it comes to migrating to databases. For some reason whenever I try to migrate git bash asks me for a password. A password I never had to enter before.
I don't know what this password could be. I tried my desktop password but that gives me the same error as if I put nothing at all.
$ npm run migrate
express-boilerplate#0.0.1 migrate C:\Users\Zackr\Documents\node\node-todo-get-post
postgrator --config postgrator-config.js
Password:
C:\Users\Zackr\Documents\node\node-todo-get-post\node_modules\postgrator-cli\postgrator-cli.js:187
rl.history = rl.history.slice(1);
^
TypeError: Cannot read property 'slice' of undefined
at C:\Users\Zackr\Documents\node\node-todo-get-post\node_modules\postgrator-cli\postgrator-cli.js:187:33
at Interface._onLine (readline.js:335:5)
at Interface._normalWrite (readline.js:482:12)
at Socket.ondata (readline.js:194:10)
at Socket.emit (events.js:315:20)
at addChunk (internal/streams/readable.js:309:12)
at readableAddChunk (internal/streams/readable.js:284:9)
at Socket.Readable.push (internal/streams/readable.js:223:10)
at Pipe.onStreamRead (internal/stream_base_commons.js:188:23) npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR!
express-boilerplate#0.0.1 migrate: postgrator --config postgrator-config.js npm ERR! Exit status 1 npm ERR! npm ERR! Failed
at the express-boilerplate#0.0.1 migrate 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!
C:\Users\Zackr\AppData\Roaming\npm-cache_logs\2021-02-17T21_50_59_429Z-debug.log
Didn't realize that the new version of postgrator-cli requires a password. I rolled back to an earlier version.
Related
I have been following the Commercial Paper tutorial from https://hyperledger-fabric.readthedocs.io/en/release-1.4/tutorial/commercial_paper.html
When I instantiate the chaincode by running the following command
docker exec cliMagnetoCorp peer chaincode instantiate -n papercontract -v 0 -l node -c '{"Args":["org.papernet.commercialpaper:instantiate"]}' -C mychannel -P "AND ('Org1MSP.member')"
I get the following error after a few minutes
Error: could not assemble transaction, err proposal response was not successful, error code 500, msg timeout expired while starting chaincode papercontract:0 for transaction
I have been digging down a bit and it seem the "dev-peer0.org1.example.com-papercontract-0" is failing
dev-peer0.org1.example.com-papercontract-0 logs show the following:
dev-peer0.org1.example.com-papercontract-0|npm ERR! path /usr/local/src/package.json
dev-peer0.org1.example.com-papercontract-0|npm ERR! code ENOENT
dev-peer0.org1.example.com-papercontract-0|npm ERR! errno -2
dev-peer0.org1.example.com-papercontract-0|npm ERR! syscall open
dev-peer0.org1.example.com-papercontract-0|npm ERR! enoent ENOENT: no such file or directory, open '/usr/local/src/package.json'
dev-peer0.org1.example.com-papercontract-0|npm ERR! enoent This is related to npm not being able to find a file.
dev-peer0.org1.example.com-papercontract-0|npm ERR! enoent
dev-peer0.org1.example.com-papercontract-0|
dev-peer0.org1.example.com-papercontract-0|npm ERR! A complete log of this run can be found in:
dev-peer0.org1.example.com-papercontract-0|npm ERR! /root/.npm/_logs/2019-02-08T11_51_20_601Z-debug.log
Have been stuck at it for two days, any help would be greatly appreciated!
Edit: The steps before this run smoothly as expected.
Also the first network simulation (./byfn.sh up) runs perfectly fine.
You need the package.json inside the directory of the chaincode. For example, the chaincode directory name is: ./Chaincode , and inside should be chaincode.js and package.json.
In the package.json, on start, in script you should put "node chaincode.js". That because the peer use npm start to execute the chaincode.
I have tried to make desktop exe for window using electron. I have run below command to generate sign version of exe:
electron-windows-store --input-directory .\\desktop\\dist\\win-unpacked --output-directory .\\desktop\\store --flatten true -a .\\resources\\desktop -m .\\desktop\\assets\\windows\\AppXManifest.xml --package-version 0.0.0.1 --package-name MoodleDesktop
But it give me below error:
> moodledesktop#3.5.1 windows.store D:\wamp64\www\moodle-desktop
> electron-windows-store --input-directory .\desktop\dist\win-unpacked --output-directory .\desktop\store --flatten true -a .\resources\desktop -m .\desktop\assets\windows\AppXManifest.xml --package-version 0.0.0.1 --package-name MoodleDesktop
You need at least Node 4.x to run this script
error: unknown option `--flatten'
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! moodledesktop#3.5.1 windows.store: `electron-windows-store --input-directory .\desktop\dist\win-unpacked --output-directory .\desktop\store --flatten true -a .\resources\desktop -m .\desktop\assets\windows\AppXManifest.xml --package-version 0.0.0.1 --package-name VedificDesktop`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the moodledesktop#3.5.1 windows.store 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! C:\Users\prawez.musharraf\AppData\Roaming\npm-cache\_logs\2019-02-12T09_50_34_214Z-debug.log
How we resolve this error??
Any help really appriciated.
as from sep 2018 the option flatten been removed
https://github.com/felixrieseberg/electron-windows-store/commit/dcc654df2ec2bb706dc4f1664aa4775ab320541e
that mean just remove it from the command and everything going to be okay!
Introduction
I trying to run rails-react-boilerplate, everything goes fine, but at the end of installation (bundle install, yarn install, rake db:create ..), command with webpack simple not working. There is a link on github repository: rails-react-boilerplate.
Error
After this command npm run webpack I get this error:
openssl config failed: error:02001003:system library:fopen:No such process
> rails-react-boilerplate#1.0.0 webpack D:\code\portfolio\liftProgress
> ./node_modules/webpack/bin/webpack.js --progress --colors
'.' is not recognized as an internal or external command,
operable program or batch file.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! rails-react-boilerplate#1.0.0 webpack:
`./node_modules/webpack/bin/webp
ack.js --progress --colors`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the rails-react-boilerplate#1.0.0 webpack 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! C:\Users\Derid\AppData\Roaming\npm-cache\_logs\2017-12-
30T07_27_37_
058Z-debug.log
openssl config failed: error:02001003:system library:fopen:No such process
where I think main problem is:
'.' is not recognized as an internal or external command,
operable program or batch file.
.. but I am at one's wits' end .. very thanks for your guidance and help!:)
This is a Windows issue, you can try omitting the ./ from the actual command on the package.json file.
Actually after doing some research, including the node executable should work cross-platform:
"webpack": "node node_modules/webpack/bin/webpack.js --progress --colors",
During npm install the following error occurs during the install. The file is located in the npm virtual repo and the npm-local repo. Both files have the same checksum, but for reasons unknown Jenkins/Artifactory build returns with an expected valued different than what is actual.
Workspace, temp dir and cache for node_modules cleaned and error remains. What would cause the variance in returned shasum/chksum values?
npm ERR! shasum check failed for /var/folders/zd/d9z45rkj01ddtxxzw_2kzbvnxnn7wh/T/npm-90754-e7f5acef/artifactory.be.sharecare.com/api/npm/npm-repo/foreachasync/-/foreachasync-3.0.0.tgz
npm ERR! Expected: 5502987dc8714be3392097f32e0071c9dee07cf6
npm ERR! Actual: 3475a95a77e4dc2d2800913e6824de77b00cd80a
npm ERR! From:
When i am installing Electron using npm install electron-prebuilt --save-dev, I am getting the following error:
Error: end of central directory record signature not found
at C:\Users\madhava\Desktop\New folder\node_modules\electron-prebuilt\node_modules\extract-zip\node_modules\yauzl\index.js:98:14
at C:\Users\madhava\Desktop\New folder\node_modules\electron-prebuilt\node_modules\extract-zip\node_modules\yauzl\index.js:342:5
at C:\Users\madhava\Desktop\New folder\node_modules\electron-prebuilt\node_modules\extract-zip\node_modules\yauzl\node_modules\fd-slicer\index.js:32:7
at FSReqWrap.wrapper [as oncomplete] (fs.js:527:17)
npm ERR! Windows_NT 6.1.7600
npm ERR! argv "C:\\Program Files\\nodejs\\\\node.exe" "C:\\Program Files\\nodejs
\\node_modules\\npm\\bin\\npm-cli.js" "install" "electron-prebuilt" "--save-dev"
npm ERR! node v0.12.4
npm ERR! npm v2.10.1
npm ERR! code ELIFECYCLE
npm ERR! electron-prebuilt#0.27.3 postinstall: `node install.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the electron-prebuilt#0.27.3 postinstall script 'node install
.js'.
npm ERR! This is most likely a problem with the electron-prebuilt package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node install.js
npm ERR! You can get their info via:
npm ERR! npm owner ls electron-prebuilt
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! C:\Users\madhava\Desktop\New folder\npm-debug.log
I had this problem when trying to install on a dodgy connection, which meant I had some bad zips left over. Solution was (on OSX at least to remove the ~/.electron folder, and run npm install electron-prebuilt again. Not sure where the zips get saved to on Windows though.
This is error is because the version of glibc on your host is too old for some of electron's dependencies. Looks like you're using Windows. I ran into this issue with Debian Wheezy The only solution I found was to install a newer version of glibc via this hack:
How to upgrade glibc from version 2.13 to 2.15 on Debian?
You'll need to do something similar with windows.
I had the same issue when i was installing electron globally.here is what i did
rm -rf ~/.electron/
rm -rf ~/.atom/
npm cache clear
npm install
after this I ran the command again..
npm install electron -g
if this doesn't work,you can use the prebuilt version
npm install electron-prebuilt
Here is the resource i used..