Skip to content

Conversation

@crocodile-dentist
Copy link
Contributor

List of changes

Traces reasons for signature validation failure

Checklist

  • My changes generate no new warnings
  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have added tests that prove my fix is effective or that my feature works

dmqcLocalServerTracer = I False,
dmqcLocalInboundGovernorTracer = I False,
dmqcDnsTracer = I False,
dmqcValidationTracer = I False,
Copy link
Contributor

Choose a reason for hiding this comment

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

It should be on by default, we don't expect many invalid messages, and once it happen the connection is closed, so we won't be flooded by them.

Suggested change
dmqcValidationTracer = I False,
dmqcValidationTracer = I True,

Comment on lines +188 to +189
instance Show (Sig crypto) where
show Sig { sigId } = "Sig crypto ... " <> show sigId
Copy link
Contributor

Choose a reason for hiding this comment

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

We shouldn't use Show for, could you just leave a TODO for adding a Display type class.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: In Progress

Development

Successfully merging this pull request may close these issues.

3 participants