Felix Lange
Felix Lange
The chaindata directory doesn't use any special permissions. You can try using `geth --datadir ... removedb`.
It seems that the engine API does not expose enough information to make `--exitwhensynced` work in all cases. In scenarios where the CL itself is also syncing, we will not...
Only the security guy... could weaken the permissions of the key file 😄
I think we should accept this!
OK then!
This works, but it will run a lot of pointless tests because most clients do not support all those syncmodes.
What we mean is: at the moment, your PR removes the check that no extra data is present. We want it to be modified so that the extra data is...
Alternative approach: When handling RPC call, launch a timer using `time.AfterFunc(timeout, callback)` where the callback will deliver the error response **if the response was not sent yet**. This can be...
Actually, it can also be done with less channels using `sync.Once` ```go var respondOnce sync.Once timeoutResponseTimer := time.AfterFunc(timeout, func() { respondOnce.Do(func () { // send timeout error }) }) response...
I'm annoyed by this message, too. This happens anytime the browser cancels loading a resource. The message is even worse on SBCL because it contains the content of the write...