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

Promote main to release: daemon roll + Iceberg-backed lake query #42

Merged
admin_emi merged 6 commits from main into release 2026-07-24 19:02:21 +00:00
Conversation 0 Commits 6 Files changed 13 +435 -39
admin_emi commented 2026-07-24 19:02:05 +00:00
Owner
Copy link

Prod roll picks up the Iceberg-backed /query and future-proof daemon rolls.

Prod roll picks up the Iceberg-backed /query and future-proof daemon rolls.
admin_emi added 6 commits 2026-07-24 19:02:07 +00:00
deploy.sh: fix the daemon-binary probe, which always dropped daemon (#33)
All checks were successful
Sync infra to hosts / sync-beta (push) Successful in 5s
Details
Sync infra to hosts / sync-prod (push) Successful in 4s
Details
secrets-guard / encrypted (push) Successful in 5s
Details
shell-lint / shellcheck (push) Successful in 7s
Details
979653f407 
docker compose config --images daemon does not filter to the named service
on this host's Compose v5.3.1 -- it prints every service's image, one per
line, in file order, so `| head -1` was silently grabbing db's image
(timescaledb) instead of daemon's. The probe then always found no
/usr/local/bin/thermograph-daemon in a Postgres image and dropped daemon
from every backend deploy, regardless of what the real backend image
contained.

Fixed by building the image reference directly from the same vars
docker-compose.yml's daemon.image: already interpolates, instead of going
through docker compose config at all.

Reproduced against beta directly: the old sequence selected the wrong
image; the new construction resolves correctly and the binary probe
passes.
Log hygiene: Alloy CPU, Loki chunks/limits, Caddy field-stripping (#36)
All checks were successful
secrets-guard / encrypted (push) Successful in 5s
Details
shell-lint / shellcheck (push) Successful in 7s
Details
Validate observability stack / validate (push) Successful in 12s
Details
0862395dda
frontend: fetch City() concurrently with the page's primary API call (#37)
All checks were successful
secrets-guard / encrypted (push) Successful in 8s
Details
shell-lint / shellcheck (push) Successful in 14s
Details
Build + push frontend image (Forgejo registry) / build-push (push) Successful in 42s
Details
Deploy frontend to beta VPS / deploy (push) Successful in 1m5s
Details
da82abda27 
MonthPage and RecordsPage each made two backend calls sequentially
(CityMonth/CityRecords, then City) where the second never depended on the
first's result. fetchWithCity launches both concurrently via goroutines
and a WaitGroup.

Verified live against a stub with an injected 400ms delay on both
endpoints: city page (1 call) and month/records pages (2 calls each) all
cost ~0.404s now, not double for the two-call pages.

Error priority preserved exactly: primary's error wins even when City
also fails, matching the old sequential code. One trade-off: City() is
now always launched even on a request about to 404 from primary, costing
one extra cheap lookup on that rare path.

Tests include a deterministic concurrency proof via rendezvous channels
(the old sequential code would deadlock this test, not just run it
slower). Full suite green under -race -count=2.
infra/forgejo: add resource limits and a leaner CI job image (#38)
Some checks failed
Sync infra to hosts / sync-beta (push) Successful in 7s
Details
Sync infra to hosts / sync-prod (push) Failing after 8s
Details
secrets-guard / encrypted (push) Successful in 7s
Details
shell-lint / shellcheck (push) Successful in 8s
Details
dcf15ea572
Roll the daemon with backend deploys in the Swarm stack (#40)
All checks were successful
secrets-guard / encrypted (push) Successful in 6s
Details
shell-lint / shellcheck (push) Successful in 7s
Details
PR build (required check) / changes (pull_request) Successful in 9s
Details
secrets-guard / encrypted (pull_request) Successful in 8s
Details
shell-lint / shellcheck (pull_request) Successful in 9s
Details
PR build (required check) / build-backend (pull_request) Has been skipped
Details
PR build (required check) / validate-observability (pull_request) Successful in 23s
Details
PR build (required check) / build-frontend (pull_request) Successful in 57s
Details
PR build (required check) / gate (pull_request) Successful in 2s
Details
578fb563a4
Merge pull request 'Promote dev to main: daemon roll + Iceberg-backed lake query' (#41) from dev into main
All checks were successful
Sync infra to hosts / sync-beta (push) Successful in 6s
Details
Sync infra to hosts / sync-prod (push) Successful in 11s
Details
secrets-guard / encrypted (push) Successful in 9s
Details
Validate observability stack / validate (push) Successful in 14s
Details
shell-lint / shellcheck (push) Successful in 7s
Details
secrets-guard / encrypted (pull_request) Successful in 9s
Details
shell-lint / shellcheck (pull_request) Successful in 8s
Details
88f5d0cce0
admin_emi merged commit a3a1209645 into release 2026-07-24 19:02:21 +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#42
No description provided.
Delete branch "main"

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?