Skip to content
This repository has been archived by the owner on Dec 4, 2024. It is now read-only.

remove panic on unexpected number of Stacks statuses updated #334

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

radicleart
Copy link
Collaborator

just removes the panic when the server is restarted and it processes all the previous mints and burns

@radicleart radicleart linked an issue Oct 28, 2023 that may be closed by this pull request
@radicleart
Copy link
Collaborator Author

After spinning up a node with this change i get lots of logging like this...

2023-10-28T15:37:38.671959Z DEBUG update: romeo::state: Ignoring Broadcasted status update for a Stacks transaction that is not acknowledged: 0000000000000000000000000000000000000000000000000000000000000000 event=StacksTransactionUpdate(0000000000000000000000000000000000000000000000000000000000000000, Broadcasted)
2023-10-28T15:37:38.672003Z DEBUG update: romeo::state: Igno anring Broadcasted status update for a Stacks transaction that doesn't have a pending task: 0000000000000000000000000000000000000000000000000000000000000000 event=StacksTransactionUpdate(0000000000000000000000000000000000000000000000000000000000000000, Broadcasted)
2023-10-28T15:37:38.672047Z DEBUG update: romeo::state: Igno anring Broadcasted status update for a Stacks transaction that doesn't have a pending task: 0000000000000000000000000000000000000000000000000000000000000000 event=StacksTransactionUpdate(0000000000000000000000000000000000000000000000000000000000000000, Broadcasted)
2023-10-28T15:37:38.672091Z DEBUG update: romeo::state: Igno anring Broadcasted status update for a Stacks transaction that doesn't have a pending task: 0000000000000000000000000000000000000000000000000000000000000000 event=StacksTransactionUpdate(0000000000000000000000000000000000000000000000000000000000000000, Broadcasted)
2023-10-28T15:37:38.672136Z DEBUG update: romeo::state: Igno anring Broadcasted status update for a Stacks transaction that doesn't have a pending task: 0000000000000000000000000000000000000000000000000000000000000000 event=StacksTransactionUpdate(0000000000000000000000000000000000000000000000000000000000000000, Broadcasted)
2023-10-28T15:37:38.672180Z DEBUG update: romeo::state: Igno anring Broadcasted status update for a Stacks transaction that doesn't have a pending task: 0000000000000000000000000000000000000000000000000000000000000000 event=StacksTransactionUpdate(0000000000000000000000000000000000000000000000000000000000000000, Broadcasted)

@friedger
Copy link
Collaborator

While this cures the symptom, I think the problem is elsewhere.

@CLAassistant
Copy link

CLAassistant commented Nov 16, 2023

CLA assistant check
All committers have signed the CLA.

…acks-statuses-updated

* main:
  test: add property-based tests for romeo asset contract
  test: add property-based tests for romeo asset contract
  test: add property-based tests for romeo asset contract
  test: add property-based tests for romeo asset contract
@CAGS295
Copy link
Contributor

CAGS295 commented Nov 17, 2023

I have a fix, but it unravels other issues. I'm waiting a bit longer until I can put the case together.

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.

Romeo exits with Unexpected number of Stacks statuses updated
4 participants