Spencer T Brody

The logs from @ukstv's reproduction look similar, but slightly different, than the logs we're seeing on the nodes running in our production environment. Those logs look like: ``` 2021-06-10T15:55:20.904-04:00 2021-06-10T19:55:20.904Z...

These logs are happening extremely consistently on an ongoing basis, not just at node startup. Seems to be happening about 2-4 times a minute. Here are some timestamps from the...

@ukstv @v-stickykeys: see above. Could this be what's happening on our ELP nodes?

@v-stickykeys @zachferland - I didn't quite follow the suggestion of removing the peers from the repo - does this make sense to you? Is this something we could try on...

This is a known issue. Updates to Ceramic streams are based on read-modify-write behavior and have no special synchronization between the read and the write. That makes them ill-suited for...

> Also, if you have an existing issue in GitHub or a similar project planning tool that we can link this or externals can search in for this in the...

FYI, here's a WIP PR for updates to the docs which explain this behavior: https://github.com/ceramicnetwork/docs/pull/141

Created https://github.com/ceramicnetwork/docs/issues/199 for this suggestion, thanks @jjperezaguinaga!

@Gutyn can you please open a post on http://forum.ceramic.network? Would be good to include the code for how you're creating and authenticating the client and how you're issuing the write,...

the change to js-ceramic isn't really signficant, the real thing that needs review is the implementation of the mapmoize package: https://github.com/ukstv/mapmoize/blob/main/src/index.ts. (note @ukstv the NPM repo doesn't link to the...