Tyler Yasaka

@haadcode Thanks! Wasn't aware of the call. I may join the next one. Looking through the notes, it seems that the conclusion is that this sort of feature shouldn't be...

I've created a PR that implements the solution I am referring to. It makes minimal code changes, and does not touch the enqueueing system (unlike my original solution). It requires...

Upon further investigation, I see that my initial approach was naive. The store `sync` method waits for heads to be replicated, but not necessarily the rest of the graph. I...

2 components are now necessary because we need one component to house the extra markup needed for validation, yet we need to one to contain the original checkbox, so that...

So, I did try putting all of this into a single component. At first I ran into the issues I mentioned in my previous comment. To clarify those issues: for...

I'm finding it challenging to easily determine when my database has finished syncing with all connected peers (i.e. when the last `replicated` event is fired). Would be useful for me...

@subhasisbanik I know what the cause of this issue is (I ran into the same thing myself). `db.load()` resolves only after the database has finished loading *from storage into memory*....

Hi @subhasisbanik I did find a solution, which requires a couple modifications to orbit-db. First, I made this change to orbit-db: https://github.com/projectaspen/orbit-db/commit/f91220d3b5a8de38389464675a4db5e00319f180 Then I made this minor adjustment to orbit-db-store:...

@cuongdo Yes I was just mentioning this to @micahalcorn . I have been experiencing the same thing. (To reproduce, just leave `npm run test:jsw` open while triggering multiple runs of...

Ok, looks like this is an even bigger problem. TravisCI tests are frequently failing with this issue. Not always, but randomly failing tests are a very bad thing. 😬