1.4 KiB
1.4 KiB
Prompt
Diagnose why the chart still showed a zero first OHLCV row after the epoch-zero timestamp repair, causing auto-y-ranging to include zero.
Response summary
Audited live 60s and 1s NativeDB files and found one exact 60s first-slot sentinel at epoch 60 with a completely zero OHLCV payload. Added narrowly scoped read and merge repair, matching incoming validation, sentinel-only startup handling, canonical reindexing, and explicit audit classification. Preserved modern all-zero bars as unclassified evidence rather than assuming all zero-priced instruments are corrupt.
Files changed
piker/storage/nativedb.py- first-slot sentinel repair and validationpiker/storage/_audit.py- sentinel classification and zero-row evidencetests/test_storage_nativedb.py- hydration, merge, and boundary regressionstests/test_storage_audit.py- sentinel and modern-zero audit regressionsai/prompt-io/opencode/20260729T041723Z_ce33deb6_prompt_io.raw.md- unedited response record
ai/prompt-io/opencode/20260729T041723Z_ce33deb6_prompt_io.md- provenance metadata and response summary
Human edits
None - generated changes have not been edited by the human.