Gateway: stabilize service entrypoint path resolution#28338
Gateway: stabilize service entrypoint path resolution#28338realriphub wants to merge 5 commits intoopenclaw:mainfrom
Conversation
Greptile SummaryThis PR stabilizes Gateway service entrypoint path resolution to prevent spurious service configuration updates and improve stability across package manager updates. Key changes:
How it works: The updated Confidence Score: 5/5
Last reviewed commit: 3cf852f |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3cf852f976
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: e16c4704d8
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
src/daemon/program-args.ts
Outdated
| if (globalEntrypoint) { | ||
| return globalEntrypoint; |
There was a problem hiding this comment.
Re-throw argv entrypoint failures before PATH fallback
If resolveCliEntrypointFromArgvPath() fails (for example, running from a checkout where dist/ is not built), this branch silently falls back to which openclaw and installs the service against that PATH binary instead of the invoking CLI. That means gateway install can bind to an unrelated global version while the user is executing a different checkout/runtime, which is a regression from the previous explicit error and is hard to diagnose.
Useful? React with 👍 / 👎.
|
Potentially related issue from another reporter: #28423 (macOS LaunchAgent entrypoint stale from entry.js to index.js until manual doctor).\n\nThis PR improves service entrypoint resolution and doctor path comparison via symlink/real path normalization, which appears in the same failure family.\n\nLinking for maintainer triage and reporter verification (not auto-closing). |
|
This pull request has been automatically marked as stale due to inactivity. |
|
Closing this as superseded. The remaining useful piece from this branch, the narrow doctor realpath normalization for gateway entrypoint comparison, landed via #43882: The broader Thanks @realriphub for the original groundwork here. |
This PR forwards commit 3cf852f from realriphub/openclaw.\n\n### Summary\n- stabilize service entrypoint path resolution for Gateway\n\nPlease review and merge into upstream main.