The command fails both on @fsmanuel's an my machine.
Compiling the contracts isn't the same as deploying something.
In the bootstrap, the contracts are compiled before this step.
* The command fails both on @fsmanuel's an my machine.
* Compiling the contracts isn't the same as deploying something.
* In the bootstrap, the contracts are compiled before this step.
bumi
(Migrated from github.com)
reviewed 2019-08-05 08:58:01 +00:00
I guess so. Frankly, I don't know what is needed and what isn't, but this one was consistently failing and nobody fixed it. So this change is more of a hotfix to get the bootstrap to work, because most people don't change the kit contract or other such contracts.
I guess so. Frankly, I don't know what is needed and what isn't, but this one was consistently failing and nobody fixed it. So this change is more of a hotfix to get the bootstrap to work, because most people don't change the kit contract or other such contracts.
bumi
(Migrated from github.com)
reviewed 2019-08-05 09:42:20 +00:00
is there an issue for that? compile-contracts works fine for me (just tested it again)
even though people won't change the kit, I assumed the kit still needs to be compiled to run the deploy script.
is there an issue for that? `compile-contracts` works fine for me (just tested it again)
even though people won't change the kit, I assumed the kit still needs to be compiled to run the deploy script.
bumi
(Migrated from github.com)
reviewed 2019-08-05 09:44:46 +00:00
if you have a fresh clone (without the build directory) you'll now get a: Error: ENOENT: no such file or directory, scandir '[...]/build/contracts' error.
so contracts need to be deployed, it probably works for you now because you had deployed contracts in the build directory.
I can not reproduce any compile error here. :(
if you have a fresh clone (without the `build` directory) you'll now get a:
`Error: ENOENT: no such file or directory, scandir '[...]/build/contracts'` error.
so contracts need to be deployed, it probably works for you now because you had deployed contracts in the `build` directory.
I can not reproduce any compile error here. :(
raucao
(Migrated from github.com)
reviewed 2019-08-05 10:49:43 +00:00
Then we need to add the complete install and bootstrap on Travis, because @fsmanuel and I both have the same compilation errors on two different operating systems with different environments.
> I can not reproduce any compile error here. :(
Then we need to add the complete install and bootstrap on Travis, because @fsmanuel and I both have the same compilation errors on two different operating systems with different environments.
bumi
(Migrated from github.com)
reviewed 2019-08-05 13:28:36 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
@@ -18,3 +18,3 @@"reset:hard": "npm run deploy:apps && npm run reset","deploy:kit": "npm run compile-contracts && aragon contracts exec scripts/deploy-kit.js","deploy:kit": "aragon contracts exec scripts/deploy-kit.js","deploy:dao": "aragon contracts exec scripts/new-dao.js",what was actually broken? are the contracts still compiled?
@@ -18,3 +18,3 @@"reset:hard": "npm run deploy:apps && npm run reset","deploy:kit": "npm run compile-contracts && aragon contracts exec scripts/deploy-kit.js","deploy:kit": "aragon contracts exec scripts/deploy-kit.js","deploy:dao": "aragon contracts exec scripts/new-dao.js",@@ -18,3 +18,3 @@"reset:hard": "npm run deploy:apps && npm run reset","deploy:kit": "npm run compile-contracts && aragon contracts exec scripts/deploy-kit.js","deploy:kit": "aragon contracts exec scripts/deploy-kit.js","deploy:dao": "aragon contracts exec scripts/new-dao.js",ok, but then we need to fix the
compile-contractscommand?at which step are the contracts compiled?
@@ -18,3 +18,3 @@"reset:hard": "npm run deploy:apps && npm run reset","deploy:kit": "npm run compile-contracts && aragon contracts exec scripts/deploy-kit.js","deploy:kit": "aragon contracts exec scripts/deploy-kit.js","deploy:dao": "aragon contracts exec scripts/new-dao.js",I guess so. Frankly, I don't know what is needed and what isn't, but this one was consistently failing and nobody fixed it. So this change is more of a hotfix to get the bootstrap to work, because most people don't change the kit contract or other such contracts.
@@ -18,3 +18,3 @@"reset:hard": "npm run deploy:apps && npm run reset","deploy:kit": "npm run compile-contracts && aragon contracts exec scripts/deploy-kit.js","deploy:kit": "aragon contracts exec scripts/deploy-kit.js","deploy:dao": "aragon contracts exec scripts/new-dao.js",is there an issue for that?
compile-contractsworks fine for me (just tested it again)even though people won't change the kit, I assumed the kit still needs to be compiled to run the deploy script.
@@ -18,3 +18,3 @@"reset:hard": "npm run deploy:apps && npm run reset","deploy:kit": "npm run compile-contracts && aragon contracts exec scripts/deploy-kit.js","deploy:kit": "aragon contracts exec scripts/deploy-kit.js","deploy:dao": "aragon contracts exec scripts/new-dao.js",if you have a fresh clone (without the
builddirectory) you'll now get a:Error: ENOENT: no such file or directory, scandir '[...]/build/contracts'error.so contracts need to be deployed, it probably works for you now because you had deployed contracts in the
builddirectory.I can not reproduce any compile error here. :(
@@ -18,3 +18,3 @@"reset:hard": "npm run deploy:apps && npm run reset","deploy:kit": "npm run compile-contracts && aragon contracts exec scripts/deploy-kit.js","deploy:kit": "aragon contracts exec scripts/deploy-kit.js","deploy:dao": "aragon contracts exec scripts/new-dao.js",Then we need to add the complete install and bootstrap on Travis, because @fsmanuel and I both have the same compilation errors on two different operating systems with different environments.
@@ -18,3 +18,3 @@"reset:hard": "npm run deploy:apps && npm run reset","deploy:kit": "npm run compile-contracts && aragon contracts exec scripts/deploy-kit.js","deploy:kit": "aragon contracts exec scripts/deploy-kit.js","deploy:dao": "aragon contracts exec scripts/new-dao.js",good idea. can you create an issue with the error you've seen? thanks