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

outbound-governor assertion failure: in progress demote hot is not subset of hot peers #3186

Closed
coot opened this issue May 26, 2021 · 1 comment · Fixed by #3580
Closed
Assignees
Labels
outbound-governor Issues / PRs related to outbound-governor

Comments

@coot
Copy link
Contributor

coot commented May 26, 2021

When running cardano-node:

cardano-node: Assertion failed
CallStack (from HasCallStack):
  assert, called at src/Ouroboros/Network/PeerSelection/Governor/Types.hs:372:5 in ouroboros-network-0.1.0.0-dc41f8ccb62033587da727ee21fb683766ae63af3fac0ec4e9d468eb5d06da1a:Ouro
boros.Network.PeerSelection.Governor.Types

This assertion corresponds to:

  . assert (Set.isSubsetOf inProgressDemoteHot   hotPeersSet)
@coot coot added the peer2peer label May 26, 2021
@coot coot added test-failure a test failure outbound-governor Issues / PRs related to outbound-governor labels Nov 14, 2021
@coot coot changed the title P2P governor assertion failure outbound-governor assertion failure Nov 17, 2021
@coot coot removed the test-failure a test failure label Nov 17, 2021
@coot coot changed the title outbound-governor assertion failure outbound-governor assertion failure: in progress demote hot is not subset of hot peers Nov 17, 2021
@coot coot linked a pull request Jan 20, 2022 that will close this issue
@coot
Copy link
Contributor Author

coot commented Jan 20, 2022

This assertion failure is fixed by #3580.

@iohk-bors iohk-bors bot closed this as completed in #3580 Jan 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
outbound-governor Issues / PRs related to outbound-governor
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants