-
Notifications
You must be signed in to change notification settings - Fork 0
feat(FAR-676): doctor full - extended checks, status --json, exit codes, --report, --fix, logs #349
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
17 commits
Select commit
Hold shift + click to select a range
c8a18cb
feat(FAR-676): doctor full - extended checks, status --json enrichmen…
c6a0164
test: platform/env guards for POSIX-only doctor probes and live-DB up…
ade5fbc
test: fix architecture test-style violations in doctor tests
1fa73ec
fix(doctor): wire silent-stub probes + logs-rotate guard (FAR-676 rev…
1ecfc25
fix(doctor): wire unstubbed port/backup/TLS probes + logs rotate guar…
183158a
fix(doctor): honest TLS-skip message when no keypair generator has sh…
084a41a
fix(FAR-676): gate child-log rotation + persist bundled PG version (r…
b629432
Merge remote-tracking branch 'origin/main' into deliver/FAR-676
1593ef0
fix(db): stop 0209 re-adding collection_install_id column owned by 0207
9c3b435
docs(db): correct 0209 migration docstring to reflect 0207 owns the c…
f119d06
fix(launcher): compare bundle/data-dir PG version on shared prefix
2a5bc6d
fix(ci): ruff-format migration 0209 and replace empty-dict assertion …
74f2ca7
Merge remote-tracking branch 'origin/main' into work
c334513
Merge remote-tracking branch 'origin/main' into deliver/FAR-676
bea6f24
Merge remote-tracking branch 'origin/deliver/FAR-676' into deliver/FA…
a145aa7
test: raise new-code coverage for FAR-676 doctor/status/logs (SonarCl…
9b8364e
fix(ci): resolve test-suite-quality violations in launcher coverage t…
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bug:
rotated = rotate_log(path)is OUTSIDE the else-branch, somodulo logs postgres --rotate(or redis) prints 'rotation applies to the app log only' and then rotates postgres.log/redis.log anyway. This contradicts the --rotate help text ('INSTEAD of reading it (app only)') and the safety design: the live-launcher guard only protects launcher.log, yet the bundled postgres/redis children write-append to their logs while running — rotating those redirects writes into the rotated-away inode (the exact hazard the comment describes). Moverotate_log+ reporting into the else-branch (or guard child rotations by liveness too), and add a test thatlogs postgres --rotatedoes NOT rotate the child log.