Skip to content

fix: prevent counting duplicate lockups in pox-5#7233

Open
brice-stacks wants to merge 8 commits into
stacks-network:pox-wf-integrationfrom
brice-stacks:fix/C-02-duplicate-lockup
Open

fix: prevent counting duplicate lockups in pox-5#7233
brice-stacks wants to merge 8 commits into
stacks-network:pox-wf-integrationfrom
brice-stacks:fix/C-02-duplicate-lockup

Conversation

@brice-stacks
Copy link
Copy Markdown
Contributor

Builds on top of #7232; just the last commit is new.

@brice-stacks brice-stacks requested review from Copilot, hstove-stacks and rob-stacks and removed request for hstove-stacks May 27, 2026 13:15
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

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

Copilot wasn't able to review this pull request because it exceeds the maximum number of lines (20,000). Try reducing the number of changed lines and requesting a review from Copilot again.

Comment thread contrib/core-contract-tests/tests/pox-5/pox-5.test.ts Outdated
@hstove-stacks hstove-stacks self-requested a review May 27, 2026 21:43
Copy link
Copy Markdown
Contributor

@hstove-stacks hstove-stacks left a comment

Choose a reason for hiding this comment

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

Oh also, it looks like the Clarigen types are off - can you run npx clarigen?

@brice-stacks
Copy link
Copy Markdown
Contributor Author

this is still based on top of #7223

Simnet does not support the bitcoin data enough to allow us to get to
the thing we want to test for in the code, so we remove the unit test
and add the check to an integration test.
@brice-stacks
Copy link
Copy Markdown
Contributor Author

Oh also, it looks like the Clarigen types are off - can you run npx clarigen?
Clarigen is updated in 2f1cfaf

@coveralls
Copy link
Copy Markdown

Coverage Report for CI Build 26399134379

Coverage increased (+0.02%) to 85.974%

Details

  • Coverage increased (+0.02%) from the base build.
  • Patch coverage: 9 uncovered changes across 2 files (48 of 57 lines covered, 84.21%).
  • 6122 coverage regressions across 96 files.

Uncovered Changes

File Changed Covered %
stacks-node/src/burnchains/bitcoin_regtest_controller.rs 37 30 81.08%
stacks-node/src/burnchains/rpc/bitcoin_rpc_client/test_utils.rs 20 18 90.0%

Coverage Regressions

6122 previously-covered lines in 96 files lost coverage.

Top 10 Files by Coverage Loss Lines Losing Coverage Coverage
stackslib/src/chainstate/burn/db/sortdb.rs 615 90.4%
stackslib/src/config/mod.rs 344 69.31%
stackslib/src/chainstate/stacks/boot/mod.rs 248 94.21%
stackslib/src/chainstate/stacks/index/storage.rs 245 80.69%
clarity/src/vm/database/structures.rs 233 77.69%
stackslib/src/chainstate/stacks/miner.rs 229 83.28%
clarity/src/vm/database/clarity_db.rs 218 80.9%
stackslib/src/burnchains/burnchain.rs 216 71.46%
stackslib/src/chainstate/nakamoto/signer_set.rs 199 69.19%
stackslib/src/core/mempool.rs 170 86.84%

Coverage Stats

Coverage Status
Relevant Lines: 220603
Covered Lines: 189662
Line Coverage: 85.97%
Coverage Strength: 17663616.59 hits per line

💛 - Coveralls

@brice-stacks
Copy link
Copy Markdown
Contributor Author

I took a look at that failing sip-31 prop test. It is definitely unrelated and it looks like just a test flakiness. Opened #7251.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants