-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Conversation
will look into this one today. @pgte does anything catch your eye there? |
I've discovered that the bug is in unixfs-engine, where instead of having
This escaped previous testing because we had disabled recursive tests due to js-ipfs-api + go-ipfs browser problems: https://github.com/ipfs/interface-ipfs-core/blob/master/src/files.js#L371-L431 If those tests are enabled, we can see that now @pgte can you take a look at this one? The new unixfs-engine code is fresh in your mind. I'll try to circle back to this tomorrow if we still haven't found a solution. |
@victorbjelkholm also, you have to unlink the added folder on this CLI tests, so that the working directory stays clean. |
@victorbjelkholm as asked by @diasdavid, added test for recursive dir using core. (will also add similar test to js-ipfs-unixfs-engine) next. |
return ipfs('files get QmUhUuiTKkkK8J6JZ9zmj8iNHPuNfGYcszgRumzhHBxEEU').then((out) => { | ||
const directory = path.join(process.cwd(), 'QmUhUuiTKkkK8J6JZ9zmj8iNHPuNfGYcszgRumzhHBxEEU') | ||
expect(fs.readdirSync(directory).length).to.be.eql(8) | ||
// TODO add assertion on content of files |
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.
@victorbjelkholm your turn, tests are passing :)
(also, make sure to unlink to delete that file, like the other tests do.
oh, github closed this PR because of the other one being merged. weird @github |
Adding a test case for recursive .get that is failing with: