chore: bump DUCKLAKE_EXTENSION_TAG to v1.0-posthog.7 - #1017
Open
fuziontech wants to merge 1 commit into
Open
Conversation
Picks up the commit-loop instrumentation (ducklake_commit_stats(), PostHog/ducklake#35) and the upstream v1.5-variegata sync incl. the partition-id remap fix on commit retries (PostHog/ducklake#36). With this tag deployed, the worker-side poller shipped in #1012 activates and duckgres_worker_ducklake_commit_* metrics start flowing. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Test Impact PlanDeterministic summary of how this PR changes tests, CI runners, and coverage-risk signals. Summary
Signals
Coverage risk: neutral or increased No coverage-reduction warnings detected. |
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.
Summary
Bumps the pinned ducklake extension from
v1.0-posthog.6→v1.0-posthog.7inDockerfileandDockerfile.worker.What the new tag carries (all CI-verified on
posthog/v1.5.5):ducklake_commit_stats()(Add commit-loop instrumentation and ducklake_commit_stats() ducklake#35) — with this deployed, the worker-side poller from feat(duckdbservice): export ducklake commit-loop stats from ducklake_commit_stats() #1012 activates andduckgres_worker_ducklake_commit_*metrics (attempts, per-cause conflicts, retries exhausted, backoff, commit latency) start flowing per catalog. This is the collision-observability baseline.hive_file_patternsupport inducklake_flush_inlined_data.Release assets (
ducklake-linux-{amd64,arm64}.duckdb_extension+ SHA256SUMS) are published and fetchable — Docker builds will resolve.Test plan
duckgres_worker_ducklake_commit_*series appear in VictoriaMetrics (probe flips from dormant to active); existingduckgres_worker_ducklake_conflict_*unchanged🤖 Generated with Claude Code
https://claude.ai/code/session_01LUnQHp46rmLKdupmDUr7kG