-
Notifications
You must be signed in to change notification settings - Fork 1.2k
refactor: use aegir #155
refactor: use aegir #155
Conversation
This is weird (on circle-ci), mind checking it?
|
@diasdavid pretty sure that is circle ci cache again :( But: https://circleci.com/gh/ipfs/js-ipfs/73 the node tests are failing (and I see that locally as well) but no idea why and pointers? |
I suspect something changed on ipfs-repo that is making it looking for the wrong filename |
Yeah, everything was working till this commit 509b4dd and only after the new js-ipfs-blocks was merged, the thing broke. |
❤️ |
✅ Browser Tests Getting close finally just missing something on the cli tests:
ping @diasdavid to lend me his brain and eyes :) |
On a fresh clone and fresh npm install
Which suggests that it is trying to use a different repo than what it should. |
One more hint, note how the cli tests, the http-api tries to read from the http repo instead of the cli repo
|
@@ -16,6 +18,10 @@ exports.start = (repo, callback) => { | |||
repo = undefined | |||
} | |||
|
|||
if (typeof repo === 'string') { | |||
repo = new IPFSRepo(repo, {stores: fsbs}) | |||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since the cli
is spawning a httpAPI by feeding a string and not a repo object, we need to convert it to become a repo object so that IPFS core can consume it (if we only had a type system!)
Now it is only the bug that the repo that should be being used is the -> /Users/ground-control/code/protocol-labs/_ipfs/js/js-ipfs/test/repo-tests-run-cli
Starting at /Users/ground-control/code/protocol-labs/_ipfs/js/js-ipfs/test/repo-tests-run-cli
# should be using the repo above
Finished loading
Swarm listening on /ip4/0.0.0.0/tcp/57946
API is listening on: http://127.0.0.1:6001
Gateway (readonly) is listening on: http://127.0.0.1:57947
Debug: internal, implementation, error
Error: Uncaught error: ENOENT: no such file or directory, open '/Users/ground-control/code/protocol-labs/_ipfs/js/js-ipfs/test/repo-tests-run-http/blocks/1220a948/1220a948904f2f0f479b8f8197694b30184b0d2ed1c1cd2a1ec0fb85d299a192a447.data'
# is trying to get the -http
`` |
return nexpect.spawn( | ||
'node', | ||
[path.join(__dirname, '../../src/cli/bin.js')].concat(args), | ||
{env} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not setting properly the IPFS_PATH
for the spawned process (if you print it from https://github.com/ipfs/js-ipfs/blob/master/src/cli/utils.js#L46-L48) you will see it is undefined.
This is causing the cli process to fallback to default dir, finding that the API might be accessible through 8080, dialling to another API instead of the one generated for their tests.
Circle is not happy, but seems travis is. LGTM :) |
Circle is never happy |
🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 |
Depends on a fresh release of js-ipfs-repo that includes ipfs/js-ipfs-repo#44