-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problems trying to run aragon app (npm run start:local) #317
Comments
Thank for reporting @PJColombo Seems the wrapper isn't downloading correctly, the script/launch-local.sh doesn't clone . I'll tested with my previously downloaded client and works fine. I'll check more in detail |
Thanks for replying @galactusss I tried to reinstall aragon cli but isn't working either, don't know what else to do. Let me know if you find out something |
Can you try this:
|
Same problem @galactusss `C:\Users\USUARIO\Documents\GitHub\aragon>npx create-aragon-app testing.aragonpm.eth react C:\Users\USUARIO\Documents\GitHub\aragon>cd testing C:\Users\USUARIO\Documents\GitHub\aragon\testing>npx aragon run Address #1: 0xb4124cEB3451635DAcedd11767f004d8a28c6eE7 (this account is used to deploy DAOs, it has more permissions) i This is the configuration for your development deployment:
(node:11244) UnhandledPromiseRejectionWarning: Error: Error: Command failed: npm run start:local npm ERR! A complete log of this run can be found in:
(node:11244) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 3) |
Oh @PJColombo I just notice that you are running on a Windows PC. Unfortunately unless you want to refactor the shell script to be in node, windows is not supported yet. If you have the chance to run a virtual matching with linux I recommend that insteed. I close this cause is not an issue. |
I don't get it, I recall creating an aragon app following the tutorial step by step with no problem months ago |
We use a shell script to launch the local Aragon client but this should be changed to be a node script. Something like this |
I'll use a virtual machine then Thanks for your help tho 👍 |
instead of deprecated ```aragon init``` aragon#74 Installing aragon with ```aragon init``` command emits the following notice: ``` ✔ Created new application foo.aragonpm.eth in foo. ℹ Use of `aragon init` is deprecated and has been replaced with `npx create-aragon-app`. ``` Running the app installed this way with ```aragon run``` command fails with ``` ✔ Start a local Ethereum network ✔ Start a local Ethereum network ✔ Check IPFS ❯ Publish app to APM ⠹ Applying version bump (major) Deploy contract Determine contract address for version Building frontend Prepare files for publishing Generate application artifact Publish foo.aragonpm.eth Fetch published repo Create DAO Open DAO error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1) ecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. ``` MacOS X, [email protected], @aragon/cli 5.3.2 Also see discussion in aragon/aragon-cli#317 on this
I created an aragon app following the tutorial. When I try to run it using
aragon run
I get this (I try to delete the ~/.aragon directory but I'm still getting the error):
Opening http://localhost:3000/#/0xF5752896F514DaA719deB22657e593565F586BBe to view your DAO (node:13072) UnhandledPromiseRejectionWarning: Error: Error: Command failed: npm run start:local "scripts" no se reconoce como un comando interno o externo, programa o archivo por lotes ejecutable. npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! [email protected] start:local:
scripts/launch-local.sh`npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start:local 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\USUARIO\AppData\Roaming\npm-cache_logs\2019-01-03T02_22_20_254Z-debug.log
(node:13072) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 3)
(node:13072) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.`
The text was updated successfully, but these errors were encountered: