fix: set working directory in nsenter for relative path support #31
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
The execute_code tool description in LibreChat doesn't specify that files must be written to /mnt/data. This PR makes that the default so the LC agent doesn't have to endure a write failure and try to work it out by itself.
Code executed via the API now runs with /mnt/data as the working directory, allowing relative file paths to work correctly.
Also, includes a change to loosen up the
is_forkci check, so that PRs within a forked repo can still trigger builds.Type of change
How Has This Been Tested?
just test-k8sChecklist: