[Issue #38243] Isolated cron agent overrides should not drop sandbox.docker defaults#8
Draft
bmendonca3 wants to merge 1 commit intomainfrom
Draft
[Issue #38243] Isolated cron agent overrides should not drop sandbox.docker defaults#8bmendonca3 wants to merge 1 commit intomainfrom
bmendonca3 wants to merge 1 commit intomainfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Original Issue
Original Issue Description
When isolated cron config resolves per-agent overrides, shallow merging can replace the entire
sandbox.dockerobject if only one nested field is overridden (for exampleimage), dropping default safety/network settings. The requested fix is nested merge behavior forsandboxandsandbox.dockerso partial overrides preserve unspecified defaults.Closes openclaw#38243