New dropA new codebase every week — fresh repo, fresh bugsSee this week's

Add ?status= filter to GET /v1/jobs/{id}/runs — feature ticket · 10xDebuggable

enhancementintermediateP2pkg/queue/queue.go, internal/api/jobs_handler.goLevel 2 · Implement a feature15 XP45–60 minutes

Add ?status= filter to GET /v1/jobs/{id}/runs

Nobody has started this yet — be first.

Business impact

The README explicitly calls out dead-letter inspection as a first-class workflow: record the full error so it's inspectable via the API, never just logged and dropped. In practice, a job with a long execution history buries the handful of dead runs someone actually cares about among hundreds of succeeded ones. Anyone triaging failures -- an on-call engineer, a support agent looking up why a customer's job stopped firing -- needs to filter straight to the failures, not page through everything and eyeball statuses.

Problem

internal/api/jobs_handler.go's listRuns already parses ?status= and calls s.queue.ListByJobFiltered(ctx, id, models.RunStatus(status), limit) when present. pkg/queue/queue.go's ListByJobFiltered is a placeholder that panics with "TODO(ticket-E2): ListByJobFiltered not implemented". Today, hitting GET /v1/jobs/{id}/runs?status=dead returns an opaque HTTP 500.

Current behavior

GET /v1/jobs/1/runs?status=dead returns HTTP 500 instead of 200.

Expected behavior

GET /v1/jobs/{id}/runs?status=dead returns only that job's dead runs, most recent first, honoring the existing limit parameter. Omitting ?status= keeps today's "all statuses" behavior.

Steps to reproduce

Run the server and call GET /v1/jobs/1/runs?status=dead.
Observe: HTTP 500 instead of a filtered 200 response.

Why this matters

This mirrors ticket 3 (ListFiltered for jobs) but on job_runs: a single-column filter added to an existing query, no new joins or pagination interaction.

Suggested approach

Look at ListByJob immediately above ListByJobFiltered in pkg/queue/queue.go for the exact query shape (columns, ORDER BY, LIMIT) to match -- ListByJobFiltered needs the same query plus a status = $N predicate.

Acceptance criteria

GET /v1/jobs/{id}/runs?status=dead returns HTTP 200 and only that job's dead runs
GET /v1/jobs/{id}/runs (no status) is unaffected
The existing limit query parameter still works in combination with status
go build ./..., go vet ./..., gofmt -l . stay clean

Verification

TEST_DATABASE_URL="postgresql://chronos:chronos@localhost:5432/chronos?sslmode=disable" go test ./tickets/tests/... -run TestTicket06 -v

Hints (0/2)

Try it without hints first — the reading is the exercise.

Working on this ticket

Work on a branch named for the ticket — that's what you'll submit.

Branch off your fork

$git checkout -b feat/list-runs-status-filter

Fix it and commit

Meet every acceptance criterion, and add a test that would have caught this.

Push the branch

$git push -u origin feat/list-runs-status-filter

Submit it below

Paste your fork URL and the branch name, with a short write-up of the root cause.

Submit your fix

Questions

Stuck on something?

Ask about anything unclear in the ticket — the maintainer and anyone who has solved it can answer. Please don't post full solutions.

No questions yet. If something in this ticket reads ambiguously, you are probably not the only one — ask.

The project

Chronos — Distributed Cron Scheduler

A "cron-as-a-service" job scheduler backed entirely by Postgres -- SKIP LOCKED leasing and advisory-lock leader election, no etcd/ZooKeeper/Consul -- twenty ways the coordination quietly breaks.

Fork on GitHub

Download

Setup

Chronos — Distributed Cron Scheduler

git clone <your-fork>
cd GolangDevTraining/chronos
docker compose up --build   # postgres + two app replicas + adminer, hot-reloading on save

Two replicas run on () and (), both against the same database; Adminer is at . Verify with and .

http://localhost:8081

app-1

http://localhost:8082

app-2

http://localhost:8090

curl localhost:8081/healthz

curl localhost:8081/readyz

export TEST_DATABASE_URL="postgresql://chronos:chronos@localhost:5432/chronos?sslmode=disable"
go test ./tickets/tests/... -run TestTicket08 -v   # a single ticket
./tickets/run_tickets.sh                           # all 20, clean pass/fail summary