Store provider wait time in Postgres

Open Beginner friendly
#108 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
82/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
postgresql, python
Domain
database

Research direction

Start with src/meridian/store/schema.sql and src/meridian/store/repo.py to see how duration_ms is defined and written. Add storage for Efficiency.upstream_wait_ms alongside it, then check the repository’s tests for store writes and history queries. Done when history queries can distinguish slow trials from provider throttling.

Written by the indexing model from the issue text.

Description

area: store enhancement size: S
Context

Efficiency.upstream_wait_ms (time spent backing off from the provider) is not stored either.

What to do

Add the column alongside duration_ms and write it.

Done when

History queries can separate slow trials from throttled ones.

Where to look

src/meridian/store/repo.py, src/meridian/store/schema.sql


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.