Raymond Cheng
Raymond Cheng
To be clear, this issue is mean to track dynamic resharding and failure recovery on the server-side. None of these should be visible to the client
We can start with running some profiling studies on application workloads
Currently, we assume 1 instance => 1 process => 1 GPU High level question: What is the best way to run multiple Talek instances (e.g. to support multiple data sizes)
Right now it's set up for chaining. e.g. leader -> follower1 -> follower2 -> etc. any server can choose to terminate the chain. Is that not sufficient?
Sure, conceptually it's essentially a frontend gateway (that can coexist with any one of the servers). So the leader = follower + frontendGateway
This is.... weird! I see the image is in the metadata, and I'm able to open those data URL links manually in my browser. So opensea has issues with some...
It looks like the HypercertForm was removed in the project? So now I see a bunch of red errors because the FormField cannot get the form props Feel free to...
Oh! Thanks for flagging that, it looks like we've been sharing access by the individual project. I just added you and @bitbeckers to the workspace. Sorry about that!
Discount my opinion, since at this current point in time, you guys have been more active than me in this repo Just wanted to share my personal experience with a...
I'd say whoever is responsible for fixing user-reported errors should be the one to make the call. The intention of the tests is to save you time, so if you're...