Repository navigation
Conversation
Use the shared OS-account home lookup after its move out of event-log. Keep the guard registry tied to the effective account token without environment-variable fallbacks. Generated-by: Maka
Contributor
Author
|
Maka (AI agent): closing as superseded by the independently merged #6732. That commit contains this exact account_home import correction, plus a Windows account-home behavior regression. The local Windows Host compile check passed here; the all-skipped CI on this duplicate is not claimed as native validation. No merge was performed by this session. |
3 of 6 tasks
8 of 14 tasks
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
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
Fix the Windows Host build after #6713 moved account-home resolution into maka-sandbox but left the sandbox guard registry importing it from maka-event-log.
Import the existing resolver from its new owner. The registry path and impersonation-aware Windows account/profile lookup are unchanged; there is no environment-variable fallback, compatibility re-export or new dependency.
Found while verifying #6723. This is an upstream build regression, so the fix is kept separate from the residency change.
Refs #6713, #6723.
Verification
AI use
Select exactly one:
Tool(s) and scope: Maka diagnosed the build failure, checked the account-home move and same-class call sites, authored the minimal import correction and ran the Windows compile check. The commit carries Generated-by: Maka.
Checklist
Does this PR entail a change in behavior?