Skip to content

Conversation

@sweatybridge
Copy link
Contributor

@sweatybridge sweatybridge commented Jan 8, 2026

What kind of change does this PR introduce?

closes #1894

What is the new behavior?

Allow users to configure database health check timeout via config.toml.

Additional context

Add any other context or screenshots.

@sweatybridge sweatybridge requested a review from a team as a code owner January 8, 2026 09:26
@coveralls
Copy link

Pull Request Test Coverage Report for Build 20812262842

Details

  • 5 of 6 (83.33%) changed or added relevant lines in 5 files are covered.
  • 7 unchanged lines in 2 files lost coverage.
  • Overall coverage decreased (-0.03%) to 56.016%

Changes Missing Coverage Covered Lines Changed/Added Lines %
internal/db/diff/pgadmin.go 0 1 0.0%
Files with Coverage Reduction New Missed Lines %
internal/storage/rm/rm.go 2 80.61%
internal/gen/keys/keys.go 5 12.9%
Totals Coverage Status
Change from base Build 20786687458: -0.03%
Covered Lines: 6848
Relevant Lines: 12225

💛 - Coveralls

@sweatybridge sweatybridge merged commit ac1c59a into develop Jan 8, 2026
17 checks passed
@sweatybridge sweatybridge deleted the timeout-config branch January 8, 2026 10:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

"database not healthy" when running db diff

4 participants