Skip to content
This repository has been archived by the owner on Sep 26, 2019. It is now read-only.

Shuffled log levels #813

Merged
merged 15 commits into from
Feb 11, 2019
Merged

Shuffled log levels #813

merged 15 commits into from
Feb 11, 2019

Conversation

rain-on
Copy link
Contributor

@rain-on rain-on commented Feb 8, 2019

No description provided.

@rain-on rain-on requested review from jframe and CjHare February 8, 2019 03:30
Copy link
Contributor

@jframe jframe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also noticed that this is being logged at info level. Think this should be debug level

NewRoundMessageValidator | No round change messages have a preparedCertificate, any valid block may be proposed.

@@ -193,18 +193,21 @@ public void handleCommitPayload(final Commit commit) {
@Override
public void handleRoundChangePayload(final RoundChange message) {
final ConsensusRoundIdentifier targetRound = message.getRoundIdentifier();
LOG.info("Received a RoundChange Payload for {}", targetRound.toString());
LOG.trace("Received a RoundChange Payload for {}", targetRound.toString());
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no need to do toString on targetRound

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done.

@@ -158,8 +158,9 @@ private void handleMessage(final Message message) {
public void handleNewBlockEvent(final NewChainHead newChainHead) {
final BlockHeader newBlockHeader = newChainHead.getNewChainHeadHeader();
final BlockHeader currentMiningParent = currentHeightManager.getParentBlockHeader();
LOG.debug("Handling New Chain head event, chain length = {}", currentMiningParent.getNumber());
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

isn't this the chain height not chain length? elsewhere is logs I think block is just used to infer block number.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated to be chain height.

@rain-on
Copy link
Contributor Author

rain-on commented Feb 11, 2019

Also noticed that this is being logged at info level. Think this should be debug level

NewRoundMessageValidator | No round change messages have a preparedCertificate, any valid block may be proposed.

went with trace - this is a really normal thing to happen, its not even debug in my opinion.

@rain-on rain-on merged commit 30f7254 into PegaSysEng:master Feb 11, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants