Skip to content

Conversation

@vmx
Copy link
Member

@vmx vmx commented Sep 9, 2019

This callbackified ipfs-repo. Almost all tests pass, except the ones for
custom locking.

Though when used with js-ipfs, the js-ipfs tests won't work. It seems
that starting up a node is stuck somewhere.

This callbackified ipfs-repo. Almost all tests pass, except the ones for
custom locking.

Though when used with js-ipfs, the js-ipfs tests won't work. It seems
that starting up a node is stuck somewhere.
@jimpick
Copy link

jimpick commented Sep 9, 2019

I’ll take a look at the js-ipfs tests.

@jimpick
Copy link

jimpick commented Sep 13, 2019

I think I know what's going on...

My build of js-ipfs with this branch of ipfs-repo was getting stuck starting mfs because it's using ipfs-mfs 0.12.2 ... which doesn't have the following changes:

ipfs-inactive/js-ipfs-mfs@c21e032

If I use ipfs-mfs from the master git branch, more tests run.

I tweaked package.json to build it from master:

"ipfs-mfs": "ipfs/js-ipfs-mfs"

@jimpick
Copy link

jimpick commented Sep 13, 2019

Here's a fix for some of the failing tests. I'll look at the other ones tomorrow.

ipfs/js-ipfs@4073e23

@achingbrain
Copy link
Member

Since ipfs/js-ipfs#2390 was merged, is this still necessary?

@achingbrain
Copy link
Member

This is no longer necessary as we are full async/await everywhere now.

@achingbrain achingbrain closed this Mar 4, 2020
@achingbrain achingbrain deleted the callbackify branch March 4, 2020 08:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants