hulk
Hi @chrisxu333 Yes, I didn't think through this issue. It's not only about how to display the information but also how to collect that perf information since we don't enable...
> We can give a tracking issue based on different types from [resp3.md](https://github.com/redis/redis-specifications/blob/master/protocol/RESP3.md) currently. Sure, it's good to separate sub-tasks by the data type, but we need to offer a...
@lryong IMHO, it's no possible to cover all scenarios in one repo. So it'd will be better to offer a way to load the custom data source, and only maintain...
@kishorenc I would like to take a loo and try to fix it if no one is on it now.
@kishorenc I guess it should cause by the stdout has the buffered but stderr is not.
@chayim Do you mean to remove ginkgo and replace it with testify assertions? If yes, it needs massive work to refactor old test cases, but we can split it into...
@caipengbo Would you mind giving some input about what you plan to improve?
@caipengbo Thanks for your input.
@caipengbo Do you mean that we can send the write batch directly instead of the RESP format？
> > Do you mean that we can send the write batch directly instead of the RESP format？ > > @git-hulk Yup, we send the write batch directly, and the...