Ronny Esterluss
Ronny Esterluss
## Expected Behavior Being able to access db in reasonable time without crashing hard. ## Context (Environment) v2.1 running on https://console.cloud.google.com/artifacts/docker/hoprassociation/europe-west3/docker-images/hoprd/sha256:4f3faffc00b266a35755d92b9e1c71b40acb16554252661816493bffc662ff7e?project=hoprassociation ## Logs https://drive.google.com/file/d/1oDIlGMNatSSHu02GK6jLuf6TFLjCtTs5/view?usp=drive_link
Nodes were restarted during automatic deployment with a different provider in the configuration file. Everything else stayed the same. logs here: https://drive.google.com/drive/folders/1RDn2CJ9iBt2RRNjTbO6g3znlZRvRlibX?usp=sharing
This draft introduces a new endowment that would allow a snap to register itself as a request middleware.
We observed the following behavior: uHTTP nodes were not listed as peers between each other. After iniating a manual ping between two of those unpeered nodes, they immediately become high...
The exit application holds an active websocket connection on HOPRd to listen to messages. When the node goes down the websocket connection breaks as expected. The node then periodically tries...
`settings.formatter.shfmt.indent_size = 4;` does not yield the correct result. Instead it generates: ``` [formatter.shfmt] command = "/nix/store/dnpapz7zjffyapcfdwbkig1b03zyyx6a-shfmt-3.10.0/bin/shfmt" excludes = [] includes = ["*.sh", "*.bash", "*.envrc", "*.envrc.*", "*.sh"] indent_size = 4...
HOPRD does not have any traffic shaping that manages throughput in an acceptable way. This leads to scenarios where a) the entry node b) any relay node c) the exit...