Truffle contract deployment stuck - javascript

Whenever i use truffle to deploy, my console outputs an empty line and gets stuck
Here is my config :
When i run truffle migrate --network ropsten the console stops and it doesn't output anything.
Any help would be appreciated
UPDATE
Now im getting this error :
Error: PollingBlockTracker - encountered an error while attempting to update latest block:
Error: getaddrinfo ENOTFOUND ropsten.infura.io

So as it turns out, Infura do not have functionality to unlock an account using the private key. I ended up moving my code back to remix.Although you cant work and develop locally with remix, it provides a great interface for deploying smart contracts from your meta mask wallet. No migration scripts required!

Related

zsh: command not found: sls

I am running a node js application with AWS.
This is server less application therefore when I am trying to install through this
https://www.serverless.com/plugins/serverless-offline
Things are working fine till here.. after that when I am trying to run sls offline I am getting this error.
zsh: command not found: sls
Can anybody help me what I am missing here. Also I have places all the access details of my AWS creads in AWS credentials.

JSON error when running react native app with expo

When I try to run my react native app on expo with expo start, it logs the qr code, but it also logs this error after some time:
Failed to construct transformer: Error: Ca
nnot parse /home/runner/kitsu-mobile-1/.nvm
/test/fast/Unit tests/mocks/project_dirs/ne
sted-both/package.json as JSON: Unexpected
end of JSON input
at Object.<anonymous> (/home/runner/kit
su-mobile-1/node_modules/metro/node_modules
/jest-haste-map/build/worker.js:167:15)
...
I cannot connect after scanning the qr code with my phone because of that error.
I am using:
node 16.2.0
npm 7.13.0
I would appreciate any help.
Very late answer, but seems we are the only 2 that had this error.
If you fill the package.json that give this error with {}, the error disappears!

Syntaxerror: Unexpected Token , in Hawk (fresh npn install)

I am in the process of learning Nodejs and WebRPC. I am for all intents and purposes, a novice.
I installed the Plivo (http://plivo.com) API for nodejs and when attempting to run it I had an issue with Const which I resolved by running my test file with --harmony appended to the start of the command, after this I have gained the error
Syntaxerror: Unexpected token ,
This error falls on line 506 of
\hawk\lib\server.js
The relevant section of code is;
const artifacts = {
ts: authorization.ts,
nonce: authorization.nonce,
host,
port,
hash: authorization.hash
};
line 506 is host,
I do not see the problem.
At this point, all I am trying to do is initialise the plivo API. I have no other calls to it.
I have deleted the hawk folder and done a fresh npm install hawk, can anyone else suggest anything?
edit:
As of writing the post, I attempted to load hawk directly in a script rather than as a dependency through plivo. It still brings up the same error so it won't be a problem with plivo.
Edit 2.
Seems it was a versioning issue. My system had v0.12 installed. I attempted to update it twice, both times the install went back to v0.12 despite uninstalling it first.
Cleared appdata\roaming\npm and appdata\roaming\npm-cache as well as deleting any remaining node files in "c:\program files" before reinstalling. I now have 8.x installed and the syntax error is no longer showing.
Thanks
Ken

meteor fails to start server in events.js with write EOF exception

When I try to start a meteor project I always get this error message (on my machine only, the project is working fine on my colleague's machines):
=> Started proxy.
=> Started MongoDB.
events.js:141
throw er; // Unhandled 'error' event
^
Error: write EOF
at exports._errnoException (util.js:907:11)
at WriteWrap.afterWrite (net.js:785:14)
Sometimes the error already shows up before mongo is stared.
In fact, I cannot start any project anymore ... :-(
It seems that I have a serious problem with my meteor installation.
I tried re-installing meteor, but no effect.
meteor reset --> no effect
Could it be a problem with a downloaded package? Where does meteor store the packages?
I really would appreaiate any hint what I can try to make it work again.
I'm using meteor on windows.

selenium webdriver manager update - npm

I tried to update the selenium webdriver using the "webdriver-manager", but i get the error as,
Error: Got error Error: read ECONNRESET from https://selenium-release.storage.googleapis.com/2.48/selenium-server-standalone-2.48.2.jar
Error: Got error Error: read ECONNRESET from https://selenium-release.storage.googleapis.com/2.48/selenium-server-standalone-2.48.2.jar
fs.js:60
throw err; // Forgot a callback but don't know where? Use NODE_DEBUG=fs
^
Error: EPERM: operation not permitted, unlink 'C:\Users\user_name\AppData\Roaming\npm\node_modules\protractor\selenium\selenium-server-standalone-2.48.2.jar'
at Error (native)
I am not sure what was the cause. I tried updating the protractor too, but no luck.
Also i tried running the command prompt as administrator and run
webdriver-manager update --ignore_ssl
Please help.
I have solved the issue as below,
// Update chrome alone
webdriver-manager update --standalone=0 --chrome --alternate_cdn http://chromedriver.storage.googleapis.com/
// Update selenium alone
webdriver-manager update --chrome=0 --standalone --alternate_cdn http://selenium-release.storage.googleapis.com/
I was facing same issue and got the below error when running update chrome driver.
Error: Got error Error: self signed certificate in certificate chain from https://chromedriver.storage.googleapis.com/2.21/chromedriver_win32.zip
I manually downloaded the driver saved it as node_modules\protractor\selenium\chromedriver_2.21.exe
and it worked. I was running it from my office network
it actually works over http as well: http://selenium-release.storage.googleapis.com/2.48/selenium-server-standalone-2.48.2.jar , just find-replace it inside the library.
Or download it manually to: node_modules/protractor/selenium
i had same problem.
Solution for me was updating node.js (best way to do it - just download latest version and install it).

Categories

Resources