Skip to content

fix(decoder): sanitize HEP timestamps for RTPengine (#909) - #911

Merged
adubovikov merged 1 commit into
homer11from
fix/909-rtpengine-date-partitions-11.0.306
Aug 4, 2026
Merged

fix(decoder): sanitize HEP timestamps for RTPengine (#909)#911
adubovikov merged 1 commit into
homer11from
fix/909-rtpengine-date-partitions-11.0.306

Conversation

@adubovikov

@adubovikov adubovikov commented Aug 4, 2026

Copy link
Copy Markdown
Member

Summary

  • Sanitize HEP Tsec/Tmsec after decode: clamp usec ≥1e6, NTP→Unix heuristic (−2208988800), fall back to receive time outside [now−10y, now+24h], and keep Timestamp/Tsec/Tmsec in sync.
  • DuckLake adapter uses sanitized hep.Timestamp so hep_proto_5_default date= partitions no longer land in 2032–2106 from bad RTPengine HEP headers (#909).
  • Bump version to 11.0.306.

Test plan

  • go test ./decoder/ (table-driven cases from RTPengine date issue #909)
  • go vet ./decoder/ ./storage/ducklake/
  • Ingest RTPengine HEP with NTP-like 0x0009 and confirm date= is today (not 2096)
  • Zero Tsec/Tmsec writes today’s partition (not 1970-01-01)
  • Existing future date=* under hep_proto_5_default still need manual cleanup

Fixes #909

Clamp invalid usec, convert NTP-as-Unix headers, and fall back to receive
time when Tsec is out of range so proto-5 date= partitions cannot explode
the catalog (fixes #909). Bump version to 11.0.306.
@adubovikov
adubovikov merged commit 959507b into homer11 Aug 4, 2026
10 checks passed
@adubovikov
adubovikov deleted the fix/909-rtpengine-date-partitions-11.0.306 branch August 4, 2026 11:37
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.

RTPengine date issue

1 participant