Skip to content

fix: MonitorLauncher DI resolution fails — empty UI on startup#403

Merged
rygel merged 1 commit intodevelopfrom
hotfix/monitor-launcher-di-resolution
Mar 21, 2026
Merged

fix: MonitorLauncher DI resolution fails — empty UI on startup#403
rygel merged 1 commit intodevelopfrom
hotfix/monitor-launcher-di-resolution

Conversation

@rygel
Copy link
Copy Markdown
Owner

@rygel rygel commented Mar 21, 2026

Summary

HOTFIX — beta.12 shows empty UI because MS DI cannot resolve the MonitorLauncher constructor.

The MonitorLauncher constructor had Func<> parameters (healthCheckOverride, processRunningOverride, etc.) that the DI container tries to resolve but can't — they aren't registered. MS DI does NOT use default parameter values.

Fix: add a public constructor taking only ILogger<MonitorLauncher> for DI. The test constructor with Func overrides is now internal.

Test plan

  • 884 tests passing
  • Build succeeds
  • Manual verification: app starts and shows provider data

🤖 Generated with Claude Code

MS DI cannot resolve Func<> constructor parameters (healthCheckOverride,
processRunningOverride, etc.) because they aren't registered in the
container. DI does NOT use default parameter values — it requires all
parameters to be resolvable.

Fix: add a public DI constructor that takes only ILogger<MonitorLauncher>.
The test constructor with Func overrides is now internal.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@rygel rygel merged commit e044c8e into develop Mar 21, 2026
18 checks passed
@rygel rygel deleted the hotfix/monitor-launcher-di-resolution branch March 21, 2026 18:25
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.

2 participants