Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Drift baselines never form on bulk-ingested SDK data (baseline null after 21k spans)

Open
#555 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
observability

Research direction

Start by reading tokenjam/core/drift.py to trace when SDK agents' baselines are computed and what triggers evaluation during bulk ingest. Reproduce the reported case with bulk-ingested spans, then verify baseline formation and drift detection on a synthetic drifting stream. Done when the root cause is documented and either bulk ingest forms baselines or the warm-up behavior is explicit and tested.

Written by the indexing model from the issue text.

Description

enhancement good first issue help wanted

Severity: Low
Model: sonnet

Severity: Low
Where: tokenjam/ — tokenjam/core/drift.py baseline computation
Observed: After ingesting 9 full agent runs (21,562 spans) into a fresh tj serve, drift baseline was null for every agent; no drift evaluation occurred. Likely baselines need accumulated history across multiple ingest passes or a compute trigger that a single bulk ingest into a short-lived server never hits. Not fully root-caused (timeboxed).
Fix direction: Investigate when/how drift baselines are computed for SDK agents; ensure a bulk-ingested or newly-onboarded agent gets a baseline within a bounded window (or document the intended warm-up), then verify drift fires on a synthetic drifting stream.
Done when: root cause documented and either baselines form after bulk ingest or the warm-up behavior is explicit and tested.
Ref: SDK benchmark dogfood (HAL trace replay), 2026-07-17.

Dominant language
Python
Stars
122
Forks
35
Avg merge
1d 18h
Merged PRs (30d)
8

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 Metabuilder-Labs/tokenjam

All issues in Metabuilder-Labs/tokenjam

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.