Skip to content

#5994 Fix path based launch for LLProcess - #6145

Merged
akleshchev merged 1 commit into
developfrom
andreyk/viewer_process_5994
Aug 17, 2026
Merged

#5994 Fix path based launch for LLProcess#6145
akleshchev merged 1 commit into
developfrom
andreyk/viewer_process_5994

Conversation

@akleshchev

Copy link
Copy Markdown
Contributor

An oversight with new boost implementation, for parity it should have been able to look for executable in PATH.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR restores prior behavior for LLProcess when launching an executable specified by name only (no directory component), ensuring it can be resolved via the environment PATH after the Boost.Process v2 migration.

Changes:

  • Resolve bare executable names through PATH using bp::environment::find_executable() before launching.
  • Add a new unit test that launches the configured Python interpreter by basename to exercise PATH-based resolution.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File Description
indra/llcommon/llprocess.cpp Adds PATH-based resolution for executables with no parent path before process creation.
indra/llcommon/tests/llprocess_test.cpp Adds a regression test validating PATH-based executable name resolution.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread indra/llcommon/tests/llprocess_test.cpp Outdated
@akleshchev
akleshchev force-pushed the andreyk/viewer_process_5994 branch from 647966c to bd3d104 Compare August 17, 2026 22:43
@akleshchev
akleshchev merged commit d4e63ae into develop Aug 17, 2026
14 checks passed
@akleshchev
akleshchev deleted the andreyk/viewer_process_5994 branch August 17, 2026 23:53
@github-actions github-actions Bot locked and limited conversation to collaborators Aug 17, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants