Conversation
Replaces the 9999-12-31 sentinel from #48 with the first partition_date written by the fixed step 04. The image carrying the fix (08d689b, then 4d73983) was deployed on 2026-09-30 after that day's nightly, which had already processed 2026-09-28 and 2026-09-29, so the next nightly (2026-10-01 15:00 UTC) writes 2026-09-30 first. Merge only after confirming 2026-09-30 in hermes_union.events_with_as_and_geoloc was written by that run. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #48. It replaces the
9999-12-31sentinel with the first partition written by the fixed step 04, soclient_to_server_path.loop_detected/unresponsive_within_asbecome non-NULL from that date on.Why 2026-09-30: the fixed image was built on 2026-09-30 at about 21:49 UTC, after that day's nightly had already processed 2026-09-28 and 2026-09-29. The 2026-10-01 15:00 UTC nightly processes 2026-09-30 first. The same date is the first processed by the corrected statistical tests (#49), and the website changelog documents it as one boundary.
Draft until confirmed. Before merging, check that:
union_pipeline_docker_20261001.logrun used image4d73983;events_with_as_and_geoloc2026-09-30 exists, and itsreverse_looprate matches the new definition (a few percent of reverse paths, not ~75%);anomaly_counts_union2026-09-30 has no group witht_test_latency.p_value = 1e-10 AND t_stat = 0.Deploy: view only. Run
create_events_enriched.sqlwithDS=hermes_union.🤖 Generated with Claude Code