Skip to content

refactor(cli): fold Detach's server.port read into HealthProbe.resolvePort#148

Merged
Sootopolis merged 1 commit into
mainfrom
wip
Jul 4, 2026
Merged

refactor(cli): fold Detach's server.port read into HealthProbe.resolvePort#148
Sootopolis merged 1 commit into
mainfrom
wip

Conversation

@Sootopolis

Copy link
Copy Markdown
Owner

What

Route Detach's detached-launch readiness-probe port through HealthProbe.resolvePort instead of its own ConfigFactory.load().getInt("server.port").

Why

After #146 gave Status and Stop a shared HealthProbe, Detach was the third copy of the server.port resolution. This folds it in so the config key lives in one place.

Behaviour-identical: application.conf defaults port = 8080, so the key always resolves — resolvePort's 8080 fallback (which Detach's bare getInt lacked) can never actually differ. Also drops the now-unused ConfigFactory import.

Testing

  • Full sbt test via pre-push hook: passed.
  • Compiles clean; TestServeLifecycle green. The port path is behaviour-preserving (8080 either way), so no new test.

Fixes

Closes the follow-up noted in the #146 review (3rd server.port copy).

🤖 Generated with Claude Code

…ePort

The `server.port` resolution was the third copy after #146 gave Status
and Stop a shared HealthProbe. Route Detach's detached-launch readiness
probe through HealthProbe.resolvePort too, so the one config key lives
in one place. Behaviour-identical: application.conf defaults `port =
8080`, so the key always resolves and resolvePort's 8080 fallback (which
Detach's bare getInt lacked) can never actually differ. Drops the now
unused ConfigFactory import.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@Sootopolis Sootopolis merged commit f786e64 into main Jul 4, 2026
1 check passed
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.

1 participant