Add tests with more than a single shard
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by locating the main core proof test and its current single-shard configuration, then trace how the Rust and recursive verifiers are selected. Run the existing proof and e2e tests before changing coverage; done means CI exercises proofs with more than one shard through both verifier paths and reaches the relevant conditional checks.
Written by the indexing model from the issue text.
Description
Currently all tests (including e2e tests) only have one shard in the main core proof, leading to some verifier codepaths and conditional constraints/checks not being exercised by CI
Ideally, this test should exercise both the rust and the recursive verifiers
- Dominant language
- Rust
- Stars
- 80
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from argumentcomputer/sphinx
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
argumentcomputer/sphinx#206 ·
-
The termination check is under-constrained due to incomplete check of "public_values.next_pc == 0". Open
Difficulty 3/5 1-2 days Newbie friendliness 72/100
argumentcomputer/sphinx#205 ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
argumentcomputer/sphinx#204 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
argumentcomputer/sphinx#188 ·
-
SHA-512 improvements Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
argumentcomputer/sphinx#181 ·
All issues in argumentcomputer/sphinx
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug team:backend track:services-maintenance
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
cowprotocol/services#4950 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gitbutlerapp/gitbutler#15998 · 1 comment ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·