Fix WSL worker callback routing#92
Conversation
Review feedback updateImplemented the requested platform separation and CI fix in commit
Verification completed:
|
Local Windows/WSL runtime verificationRetested Results:
This confirms the explicit Windows command works in the real local stack, not only in Make dry-runs and CI. |
|
Fresh Windows/WSL installation verification update:
The complete fresh stack finished with 10 tmux sessions and 0 non-ready Kubernetes pods. Companion installer fixes discovered by this clean run are documented in highcard-dev/druid-local#3 and highcard-dev/monorepo#315. |
|
Implemented and re-verified the requested feedback on commit
Fresh validation after the split:
I also refreshed the PR description so it matches the explicit Windows command that is actually implemented. |
|
Summary
make watch-windowsentrypoint for Docker Desktop development through WSL2make watchbehavior unchanged for native Linux and macOSRoot cause
Under Docker Desktop with the daemon running inside WSL2,
host.k3d.internalresolves to the Windows-side Docker gateway rather than the daemon's current WSL address. Kubernetes materialization workers could pull artifacts but could not deliver completion callbacks, so deployments remained locked and the unlock request eventually timed out.Review feedback addressed
Platform-specific behavior is now explicit and additive: Windows users select
make watch-windows; the normalmake watchpath contains no Windows/WSL auto-detection. Fork pull requests also no longer enter the prerelease job that depends on repository credentials.Validation
bash -n scripts/watch-windows.shgo test ./...ScrollDeploymentreachedActiveDeliberately separate work
The Docker build-cache optimization is not part of this feedback PR. It is isolated in #93 so routing fixes and performance work can be reviewed independently.