Skip to content

fix(history): keep the published adjusted close within Yahoo float noise - #42

Merged
daggerok merged 2 commits into
mainfrom
fix/adjclose-noise
Oct 13, 2026
Merged

daggerok merged 2 commits into
mainfrom
fix/adjclose-noise

Conversation

@daggerok

Copy link
Copy Markdown
Owner

What changed

  • chore(data): update ARK ETF data
  • fix(history): keep the published adjusted close within Yahoo float noise

Why

Yahoo returns adjclose as float32 and its last digits move with the request's period2, so a value on a cent boundary (31.544998 vs 31.545001) rounded to a different cent on each run: a rerun with identical upstream data rewrote history pages and marked funds updated, against the zero-diff rule. The published cent is now kept while the raw value stays within 0.005 + ADJ_CLOSE_NOISE (1e-4) of it; real changes are still written. Same rule as AAM

How it was checked

  • bun test: 40 pass (new two-run jitter test fails on the old code)
  • bun build (scripts/update-data.ts, src/main.tsx), bun run build, git diff --check
  • etf-std check-readme, check-workflow, check-pages, check-scripts; tc/check.sh type check clean
  • live run TICKERS= twice: the second run leaves git status unchanged

@daggerok
daggerok merged commit 86855b2 into main Oct 13, 2026
1 check passed
@daggerok
daggerok deleted the fix/adjclose-noise branch October 13, 2026 06:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant