fix/164-health-and-logging-resilience #167
myrmidex
commented
Owner
No description provided.
myrmidex
added this to the v1.4.3 milestone
myrmidex
added the bug
label
myrmidex
added 3 commits 2026-09-26 14:00:05 +02:00
164 - Log exceptions to a non-database fallback
9247db3ed1
164 - Fail the health check when the database is unreachable
59d12d6703
164 - Exit on database timeout and supervise the workers
All checks were successful
CI / ci (pull_request) Successful in 1m59s
Details
myrmidex
added 1 commit 2026-09-26 14:15:43 +02:00
164 - Add the v1.4.3 changelog section and bump the README pin
All checks were successful
CI / ci (pull_request) Successful in 1m51s
Details
Build and Push Docker Image / build (push) Successful in 3m13s
Details
CI / ci (push) Successful in 2m12s
Details
myrmidex
merged commit b792ee7478 into release/v1.4.3
myrmidex
deleted branch fix/164-health-and-logging-resilience
myrmidex
referenced this pull request
App reports healthy while the database is unreachable and Horizon is dead #164
No reviewers
Labels
No labels
bug
devops
duplicate
enhancement
good first issue
layout
next major release
next minor release
question
research
testing
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: lvl0/fedi-feed-router#167
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/164-health-and-logging-resilience"
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?