A JS client library for the IPFS Cluster HTTP API.
Check it out here: ipfs-cluster-api
@hector @kishansagathiya @zenground0 @lanzafame
I would love your feedback
A JS client library for the IPFS Cluster HTTP API.
Check it out here: ipfs-cluster-api
@hector @kishansagathiya @zenground0 @lanzafame
I would love your feedback
@hector
I have implemented all the commands that I saw in the Go implementation.
I am facing an issue in the add
command. Can you check it out?
You can start by running the add.spec.js. Even a hint for âhow to solve it?â will be great
hi, whatâs the error? Add requires a multipart request and returns, by default, a streaming response. It is very similar to what js-ipfs-api
does to add to IPFS (just different response objects and different query arguments).
I donât navigate javascript good enough to say whatâs happening. Seems youâre writing after the stream is closed, which might suggest it sent back an error of some kind. Maybe the cluster peer logs something.
Np. Thanks for the help
I will try to fix it. BTW do you know anyone who can look into it?
Can @alanshaw look into it?
P.S.: I am sorry if I am bugging you guys a lot
Itâs fixed!
Will be releasing v0.0.3 with all the functions.
Seems like the Go REST APIs for the add
method doesnât return the CIDs
The line here returns nil
as response for the add
request.
Is there any way I can get the CID on adding the data to the cluster?
Again, I am sorry if I am bugging you a lot
Not sure if this is related but thereâs an issue in 0.4.19 that means it doesnât return all CIDs when adding multiple files.
Thanks for informing.
Will keep an eye on that
Released v0.0.3
That line returns a bad request error. The error should contain more info about why.
Yes, I checked the response from the add
API using Postman and it was giving the CID indeed.
I tried a lot, but I am not able to figure out what am I missing(it adds & pins the data to the cluster, but the final response is missing the CIDs.). I have added an issue for the same.
I would love some help here It seems to be the final glitch remaining in the ipfs-cluster-api
.
After 3 straight hours of debuggingâŚFINALLY found the culprit.
Anyways, will fix the issue, and update the docs accordingly.
Will also do some cleanups.
Will release v0.0.4 soon.