CMCDragonkai

I feel like the suites need to be named better.

#736 although is closed, I don't think our focus has entirely shifted from this. This is still a necessary, but I'll expand more on this on review of R&D 2023...

I expect to promote this issue to a "Project" as it something that would fit onto a roadmap. As per the discussion on the Project Graph concept - pipeline parallelism...

Using deadlines right now is tricky due to our async start ops in the client interceptor: https://github.com/MatrixAI/js-polykey/issues/249#issuecomment-991999605. May not affect agent service for now due to lack of any interceptor.

This should be integrated into the design in #297.

In our new RPC design, we are envisioning the ability for the server to call back the client while handling the client's call. This should replace the duplex stream being...

When working on pagination in Prism we discovered one UI/UX issue. > Noticed a bug in pagination. Actually I think I saw this before. The problem is that you're on...

This should be reviewed with respect to push-pull dataflow and control flow. ## Push vs Pull Push vs pull is 2 paradigms of "reactivity" (https://en.wikipedia.org/wiki/Reactive_programming). These concepts are applicable widely...

This is being pulled from #327 to here: > 1. Refactor `src/agent/service/nodesChainDataGet.ts` to instead be `src/agent/service/sigchainClaimsGet.ts` and this should also receive pagination parameters. This includes `seek`, `limit` and `order`. The...

With the transition to JSON RPC, this is still valid. We will still be returning collection data as a stream of individual JSON messages. However we will need to take...