'add' command doesn't return the CID for the added data.

[vasa-develop]

In v0.0.3 when we do:

cluster.add(CID, (err, res) => {
    console.log(res)
})

We get an empty array: []

Somehow we aren't getting the CID object(which can be accessed using a normal POST request).

Here is what I have found:

• On running the test for 'add', this line is supposed to get the CIDs. But it's NOT getting any CIDs.

[hsanjuan]

I think the problem is here: https://github.com/ipfs/js-ipfs-http-client/blob/master/src/utils/file-result-stream-converter.js#L38

That converter is expecting "add" objects as IPFS returns them, but cluster returns slightly different ones ("hash" is "cid" and "size" is a number and not a string).

[vasa-develop]

I think the problem is here: https://github.com/ipfs/js-ipfs-http-client/blob/master/src/utils/file-result-stream-converter.js#L38

That converter is expecting "add" objects as IPFS returns them, but cluster returns slightly different ones ("hash" is "cid" and "size" is a number and not a string).

What a coincidence...I just found this too ;)

It's working now! BTW, thanks for the quick response.

[d7laungani]

i am having this same issue in v0.09 @vasa-develop

[marwyn-the-developer]

I am also facing the same issue in v0.0.9. The answers provided are not comprehensive since the link returns a 404 message.

[hsanjuan]

@vasa-develop any ideas?

[danazkari]

I'm also having issues if I try to send just the buffer, instead I had to send an object with a path key, eventhough that key value is not used for anything useful in the IPFS context

const res = await ipfs.add({path:'dummy-name', content: fileBuffer})
// res -> [ { path: 'dummy-name', hash: '...', size: 15 } ]

So for now that's what I'm doing, because if I give it just the buffer, then it just returns an empty array.

Hope this helps someone!

[vasa-develop]

sorry guys, my notifications were turned off. So I missed the messages

[NadeeraM]

I commented following if condition in FileResultStreamConverter and then it works. But not sure why that constrain is there.
In _transform ->

if (!obj.name) {
return callback()
}

Then it returns object with empty path attribute.

[ { path: '',
hash: 'QmRHza6PjWyFpCdPZcafRybrjyaqQC2fnNfNesd7oEirid',
size: 22 } ]