Skip to content
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

Jump to bottom

Fixed log when punishing a node by address #1772

Merged
merged 1 commit into from May 19, 2022
Merged

Fixed log when punishing a node by address #1772

merged 1 commit into from May 19, 2022

Conversation

illuque-iov
Copy link

Description

Motivation and Context

How Has This Been Tested?

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • Tests for the changes have been added (for bug fixes / features)
  • Requires Activation Code (Hard Fork)
  • Other information:

@illuque-iov illuque-iov force-pushed the peer_scoring_fix_log_punish_address branch from 84209ec to 47286be Compare May 19, 2022 10:07
@sonarcloud
Copy link

sonarcloud bot commented May 19, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

80.0% 80.0% Coverage
0.0% 0.0% Duplication

@illuque-iov illuque-iov merged commit 52cbaa6 into peer_scoring_review_feature May 19, 2022
@aeidelman aeidelman added this to the Hop v4.1.0 milestone Jun 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@Vovchyk Vovchyk Vovchyk approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
Hop 4.1.0
Development

Successfully merging this pull request may close these issues.

None yet
4 participants
@illuque-iov @Vovchyk @aeidelman @illuque