Test the replay stamps of generated tasks
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
Research direction
Start by reading replay/build.py around line 221 and replay/authoring.py around line 141 to understand how generated tasks receive provenance stamps. Find the relevant tests for these task-generation paths and check that they fail if the stamps are removed. Done when tests verify the generated tasks retain the expected provenance stamps.
Written by the indexing model from the issue text.
Description
Raised in the review of PR #800 (intel/dokimi), thread PRRT_kwDOVBg7g864ZXn1.b: https://github.com/intel/dokimi/pull/800
replay/build.py:221 and replay/authoring.py:141 stamp provenance generated:dokimi-tasks-generate; no test fails when the stamps are removed. Outside this PR's change set.
Not fixed in PR #800: it is outside the lines that PR changes (another component, a design change, or too large for the round).
- Dominant language
- Python
- Stars
- 39
- Forks
- 13
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 519
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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 intel/dokimi
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
dgunning/edgartools#2019 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
topoteretes/cognee#6818 · 1 comment ·
Maintainers usually reply within 1 day
-
source_verification_agent: no outcome when the publisher confirms a work but its DOI resolves to a different recordPossibly taken @pinjun99 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Imbad0202/academic-research-skills#1159 · 1 comment ·
Maintainers usually reply within 1 day
-
[Bug]: DoubleMLData.from_arrays checks the treatment d with force_all_x_finite instead of force_all_d_finitePossibly taken @leninworld claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
DoubleML/doubleml-for-py#471 ·
Maintainers usually reply within 1 day
-
bug needs-triage
Difficulty 1/5 Under an hour Newbie friendliness 65/100
superdesigndev/treg#1879 ·
Maintainers usually reply within 1 day