Figure out annotator cache reading issue
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 15/100
Research direction
The issue body names no files, tests, or entry points. Start by locating the annotator cache reading code in the repository and reproduce the reported behavior, then identify the expected cache-reading result and add or update coverage for it. Done means the cache is read correctly and the relevant test passes.
Written by the indexing model from the issue text.
Description
This issue has no description.
- Dominant language
- Python
- Stars
- 134
- Forks
- 36
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 17
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 mlcommons/modelbench
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
mlcommons/modelbench#1659 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
mlcommons/modelbench#1656 ·
-
Difficulty 2/5 Half a day Newbie friendliness 84/100
mlcommons/modelbench#1629 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
mlcommons/modelbench#1660 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
mlcommons/modelbench#1658 ·
All issues in mlcommons/modelbench
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100