Round-trip test for saving and loading a run archive

Open Beginner friendly
  • Is something wrong?
#149 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
85/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
python
Domain
backend, testing

Research direction

Start with src/meridian/manifest/store.py to see how saving and loading handle the run manifest and result; read CONTRIBUTING.md for project guidance. Add tests that save to a temporary directory, load the run and compare both values, then cover a missing file and a corrupt file. Done means the round trip and both error cases are asserted.

Written by the indexing model from the issue text.

Description

area: tests good first issue size: S tests
Context

manifest/store.py writes a run's manifest and result to disk and reads them back for replay, with about a third covered by unit tests.

What to do

Save a run to a temp directory, load it back, and assert both are equal; also test loading a directory with a missing or corrupt file.

Done when

Saving and loading are pinned, including the error cases.

Where to look

src/meridian/manifest/store.py

New here? Read CONTRIBUTING.md and comment on this issue to say you are taking it.

Generated by Claude Code

Dominant language
Python
Stars
0
Forks
0
Avg merge
1h 54m
Merged PRs (30d)
14

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from patsypppe/meridian

All issues in patsypppe/meridian

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.