Repository navigation
cre-7120: decode core defaults per call to avoid shared mutable state #24052
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
mchain0
wants to merge
1
commit into
develop
Choose a base branch
from
cre-7120
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+51
−8
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we fix this in
SetFrom? That is already meant to be doing a deep clone.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like we just got sloppy with setting pointers instead of copying values? I think we want to fix that regardless
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suspect that it often hasn't mattered in the past since we would just point to a new place rather than update the value anyways.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sorry, do you mean a fix like #24059 ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we can cover the entire problem in SetFrom. CoreDefaults() decodes coreTOML fresh each call - every value in the returned tree is a brand-new allocation from the decoder. This is a complete deep copy by construction — no aliasing anywhere, including URL internals and slice elements.
I experimented with SetFrom, copying within like:
but that would only de-reference only one layer, it's a shallow copy of the value: anything the value contains by reference still aliases the source - e.g. commonconfig.URL's inner *url.Userinfo, slice/map elements', etc.
Doing full generic copy in SetFrom as truly recursive clone would be always flawed in this case: reflection-based recursive cloner, it would stop at leaves it can't safely clone - e.g. commonconfig.Duration (unexported d time); marshal->unmarshal round-trip would loose fields with "-" (e.g. Core.AppID uuid.UUID).
Current codebase doesn't support deep clone copy cleanly today.
The only true full-deep-copy primitive I can see here is TOML decode.
If you agree the best course of action imho would be to keep per-call decode, and maybe add a doc comment on Core.SetFrom (or the toml package) stating the actual contract: "overlay merge; copies pointers for set fields — the source must be short-lived or caller-owned; do not alias long-lived globals through it"