gz-c
gz-c
The problem is when the object to print has a mutex, and another goroutine is locking or unlocking the mutex, the sprintf will race. There is not a clear solution...
Note: the same race condition is still there, and always has been. It became more likely to occur with PR #596. This PR restores the order of sprintf calls to...
A JSON object that contains stats collected from the database
whatever boltdb exposes in its stats method, and also the number of items in buckets if this is not in the stats
@olemis can we tie this in to prometheus?
This can be reproduced by syncing a new blockchain and trying to ctrl+c at the right time. ExecuteSignedBlock is a relatively slow operation so you're likely to trigger the problem.
@Senyoret1 is it possible to do this, or should it be closed?
There is no CSRF for `GET` requests
The ability to disable all logging would be useful. This should be done first.
https://github.com/spf13/viper