Jinemi/thermograph
4
0
Fork 0
Code Issues 2 Pull requests 3 Projects Releases Packages Wiki Activity Actions

Fix lake extension bake user; disable the daemon healthcheck in the stack #30

Merged
admin_emi merged 1 commit from fix/lake-ext-daemon-health into dev 2026-07-24 03:47:40 +00:00
Conversation 0 Commits 1 Files changed 2 +11 -3
admin_emi commented 2026-07-24 03:46:25 +00:00
Owner
Copy link

First-prod-stack-deploy findings: httpfs baked as root is invisible to the uid-10001 lake (all /query 500); stack daemon lacked compose's healthcheck disable (Swarm restart loop). Prod mitigated live; this is the durable fix.

First-prod-stack-deploy findings: httpfs baked as root is invisible to the uid-10001 lake (all /query 500); stack daemon lacked compose's healthcheck disable (Swarm restart loop). Prod mitigated live; this is the durable fix.
admin_emi added 1 commit 2026-07-24 03:46:26 +00:00
Fix lake extension bake user; disable the daemon healthcheck in the stack
All checks were successful
PR build (required check) / changes (pull_request) Successful in 5s
Details
secrets-guard / encrypted (pull_request) Successful in 6s
Details
shell-lint / shellcheck (pull_request) Successful in 6s
Details
PR build (required check) / build-frontend (pull_request) Has been skipped
Details
PR build (required check) / validate-observability (pull_request) Has been skipped
Details
PR build (required check) / build-backend (pull_request) Successful in 43s
Details
PR build (required check) / gate (pull_request) Successful in 2s
Details
ec0bb42258 
Two first-prod-stack-deploy findings: DuckDB extensions install to the
invoking user's ~/.duckdb, so the root-time httpfs bake left the uid-10001
lake unable to LOAD it (every /query 500'd); and the stack file never
disabled the image healthcheck for the daemon, so Swarm killed the healthy
gateway every ~100s (compose already disabled it). Bake now runs as the
runtime user; the stack matches compose. Prod mitigated live with
--no-healthcheck pending this landing.
admin_emi merged commit eaaa4f1ad9 into dev 2026-07-24 03:47:40 +00:00
admin_emi deleted branch fix/lake-ext-daemon-health 2026-07-24 03:47:41 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
  
Compat/Breaking

Breaking change that won't be backward compatible

  
Kind/Bug

Something is not working

  
Kind/Documentation

Documentation changes

  
Kind/Enhancement

Improve existing functionality

  
Kind/Feature

New functionality

  
Kind/Security

This is security issue

  
Kind/Testing

Issue or pull request related to testing

  
Priority
Critical
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Medium
The priority is medium

  
Reviewed
Confirmed
Issue has been confirmed

  
Reviewed
Duplicate
This issue or pull request already exists

  
Reviewed
Invalid
Invalid issue

  
Reviewed
Won't Fix
This issue won't be fixed

  
Status
Abandoned
Somebody has started to work on this but abandoned work

  
Status
Blocked
Something is blocking this issue or pull request

  
Status
Need More Info
Feedback is required to reproduce issue or to continue work

No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Jinemi/thermograph#30
No description provided.
Delete branch "fix/lake-ext-daemon-health"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?