We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Last month I have started testing the idea of improving visualization and wrote a simple Poc #17779
This required improvements in the porcupine library we are using so I send a PR there anishathalye/porcupine#17. During the discussion I clarified what I would like to achieve anishathalye/porcupine#17 (comment).
@anishathalye is so awesome that they implemented the my whole idea anishathalye/porcupine#18
We need to ensure that new API is usable by etcd and provide feedback.
TODO:
Show more complete view in the visualization of robustness tests. This should allow us to show failed requests, injected failures, leader changes.
The text was updated successfully, but these errors were encountered:
cc @MadhavJivrajani @siyuanfoundation @fuweid
Sorry, something went wrong.
@serathius, is this now superseded by #19029? Do you think we should close this?
Ups, right.
No branches or pull requests
What would you like to be added?
Last month I have started testing the idea of improving visualization and wrote a simple Poc #17779
This required improvements in the porcupine library we are using so I send a PR there anishathalye/porcupine#17. During the discussion I clarified what I would like to achieve anishathalye/porcupine#17 (comment).
@anishathalye is so awesome that they implemented the my whole idea anishathalye/porcupine#18
We need to ensure that new API is usable by etcd and provide feedback.
TODO:
Why is this needed?
Show more complete view in the visualization of robustness tests. This should allow us to show failed requests, injected failures, leader changes.
The text was updated successfully, but these errors were encountered: