AnomalRoil
AnomalRoil
As I see it, you have three solutions: ## Simple and easy solution You can simply avoid relying on the chain: you don't need the full chain to verify a...
Confirmed in 1.4+ by @CluEleSsUK
We'll need to confirm whether this is still the case now that we merged #798 and have changed the way we handle the follow/sync.
I think this cannot happen anymore, but I'm not sure what were the steps to reproduce it?
I think I'll try to refactor this to integrate it with the notion of "debug logs" of GHA: https://docs.github.com/en/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging Because the debug logs are quite verbose and not necessary in...
If you need this, feel free to re-open. For now we expect the client to handle retries in a timely fashion.
Drand is now meant to be run in a closed environment, multiple users on the same machine should all be properly authorized and their action logged anyway.
Good, it confirms the issue really is the way we handle TLS.
It will also panic when using a control port that is already used (e.g. by another node). We should error out and exit gracefully with a useful error message instead.
Fixed in #1030: ``` $ ./drand start --tls-disable --folder ./local-tests/b2 --private-listen 127.0.0.1:7002 --control 7002 -verbose drand 1.4.6-testnet (date 07/09/2022@20:09:45, commit a2a2257) 2022-09-13T16:11:23.048+0200 INFO 127.0.0.1:7002 core/drand_daemon.go:115 {"network": "init", "insecure": true} 2022-09-13T16:11:23.049+0200...