-
Notifications
You must be signed in to change notification settings - Fork 20.4k
New issue
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
suggestion: miner hash rate logging flexibility #518
Comments
nolash
pushed a commit
to nolash/go-ethereum
that referenced
this issue
May 11, 2018
…pgrade swarm/network: revert Debug upgrade
ngtuna
added a commit
to ngtuna/tomochain
that referenced
this issue
May 29, 2019
Add order pending db and fix process order when prepare new block.
tony-ricciardi
pushed a commit
to tony-ricciardi/go-ethereum
that referenced
this issue
Jan 20, 2022
This limits the number of round change messages in a single sequence for a validator to one. * Update message set debug printing * Removes view from message set * Adds remove from message set function * Adds MaxOnOneRound function * Updates round change set strucuture * Updates rcs Add function * Updates rcs clear function * Updates rcs MaxRound function * Updates rcs String function * Updates rcs getCertificate function * Updates handleRoundChange function * Updates round change test * Updates comments and removes extra debug info * Adds thought on when a new round change set can be generated * Only reset round change set on new sequence * PR Feedback
maoueh
pushed a commit
to streamingfast/go-ethereum
that referenced
this issue
Dec 9, 2022
* Added script to generate config.toml fromstart.sh (ethereum#518) * added go and bash script to get config out of start.sh and updated flagset.go * changed 'requiredblocks' flag back to 'eth.requiredblocks' * updated script * changed 'requiredblocks' flag back to 'eth.requiredblocks' * updated tests, and removed requiredblocks from json and hcl * addressed comments * internal/cli/server: fix flag behaviour (ethereum#529) * remove setting maxpeers to 0 for nodiscover flag * set default prometheus and open-collector endpoint * skip building grpc address from pprof address and port * fix: linters * fix and improve tests * use loopback address for prometheus and open-collector endpoint * add logs for prometheus and open-collector setup * updated the script to handle prometheus-addr * updated builder/files/config.toml Co-authored-by: Pratik Patil <pratikspatil024@gmail.com> Co-authored-by: Manav Darji <manavdarji.india@gmail.com>
maoueh
pushed a commit
to streamingfast/go-ethereum
that referenced
this issue
Jan 6, 2023
* added go and bash script to get config out of start.sh and updated flagset.go * changed 'requiredblocks' flag back to 'eth.requiredblocks' * updated script * changed 'requiredblocks' flag back to 'eth.requiredblocks' * updated tests, and removed requiredblocks from json and hcl * addressed comments
s1na
pushed a commit
to s1na/go-ethereum
that referenced
this issue
Dec 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Can miner hash rate logging be disabled or made configurable in some way? It clutters the logs, making other important logs more difficult to see in development, such as
2015/03/17 19:19:00 [MINER] TX (3bc4be4f) failed. Transaction will be removed
2015/03/17 18:26:45 [BLOCK] TX err: stack underflow (1 <=> 4)
2015/03/17 19:36:38 [MINER] Hash rate: 71 Khash
2015/03/17 19:36:40 [MINER] Hash rate: 71 Khash
2015/03/17 19:36:42 [MINER] Hash rate: 71 Khash
2015/03/17 19:36:44 [MINER] Hash rate: 68 Khash
2015/03/17 19:36:46 [MINER] Hash rate: 61 Khash
2015/03/17 19:36:48 [MINER] Hash rate: 57 Khash
2015/03/17 19:36:50 [MINER] Hash rate: 56 Khash
2015/03/17 19:36:52 [MINER] Hash rate: 56 Khash
2015/03/17 19:36:54 [MINER] Hash rate: 54 Khash
2015/03/17 19:36:56 [MINER] Hash rate: 52 Khash
2015/03/17 19:36:58 [MINER] Hash rate: 53 Khash
2015/03/17 19:37:00 [MINER] Hash rate: 54 Khash
2015/03/17 19:37:02 [MINER] Hash rate: 53 Khash
2015/03/17 19:37:04 [MINER] Hash rate: 54 Khash
The text was updated successfully, but these errors were encountered: