[Feat request/coordinator] Record prover performance metrics into `prover_task` table
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
The issue body names no files, tests, or entry points. Start by locating the prover coordinator and the prover_task table schema, then trace where prover performance data is available. Done means the requested performance metrics are recorded in prover_task and the relevant behavior is covered by the project’s existing tests.
Written by the indexing model from the issue text.
Description
This issue has no description.
- Dominant language
- Go
- Stars
- 741
- Forks
- 632
- 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 scroll-tech/scroll
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
scroll-tech/scroll#1751 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
scroll-tech/scroll#1042 · 4 comments · 2 reactions ·
All issues in scroll-tech/scroll
Similar issues
-
kind/bug needs-triage
Difficulty 1/5 Under an hour Newbie friendliness 72/100
matrixorigin/matrixone#29223 ·
-
needs-acceptance wg/data-plane-networking
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vllm-project/semantic-router#4024 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
alexgorbatchev/dotfiles#107 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100