Export auth on browser panel sync#912
Merged
Merged
Conversation
harminius
changed the title
MarcelGeo
approved these changes
May 18, 2026
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
2 participants
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
Fixes #911 and #913.
ClientError(HTTP 404), becauseAuthSync().export_auth()hitsclient.project_info()on the wrong server before anyserver-match check runs.
AuthSync().export_auth()was only invoked from the toolbar Sync entry point; the Browser-tree sync skipped it entirely, so a user who updated credentials and synced from the Browser panel never pushed the new auth file.Fix
Move
AuthSync().export_auth(self.mc)intoMerginProjectsManager.project_status()— the chokepoint that both sync ways already flow through.