Spencer T Brody
Spencer T Brody
Thanks for the report. We are working on upgrading our ceramicnetwork/go-ipfs-daemon package to use the latest version of kubo. Will report back when that is complete
> That actually will bring http client behaviour on par with Ceramic Core. Even without using CommitIDs there is a behavior difference between the http client and Ceramic core. In...
Ping @ukstv, this is getting in the way of testing the PR I am working on now
@oed as long as we have them around we will continue to get questions about them, and people will continue to want to use them in production. This will cause...
This probably just needs us to regular a signal handler and trigger graceful shutdown (call `ceramic.close()`) when we receive a SIGTERM or other expected signals
Possibly related to https://github.com/ceramicnetwork/js-ceramic/issues/9?
Hmm, I'm not seeing this error. The version of IPFS that Ceramic relies should be using IPFS repo version 10. If you're seeing it try to use version 11, that...
@boneyard93501, same questions as I asked the original poster of this issue: The version of IPFS that Ceramic relies should be using IPFS repo version 10. If you're seeing it...
@jacksonConrad, this error usually means you have an ipfs repo created by a newer version of ipfs than ceramic currently supports. > originally I had ipfs v0.11.0. I uninstalled that,...
Sorry, these libraries aren't really ready to use yet and may have bugs or rough edges. That error is from a mismatch between the client and server libraries. Make sure...