Skip to content

fix(database): synchronize repo manager snapshots - #16774

Open
dajiaohuang wants to merge 1 commit into
firebase:mainfrom
dajiaohuang:fix/database-repo-manager-map-lock
Open

dajiaohuang wants to merge 1 commit into
firebase:mainfrom
dajiaohuang:fix/database-repo-manager-map-lock

Conversation

@dajiaohuang

Copy link
Copy Markdown

Summary\n- Snapshot per-config and all-config repo arrays while holding the shared configs monitor.\n- Release the monitor before interrupt/resume/dispose side effects.\n- Snapshot and remove a config entry atomically during disposal.\n\nThis closes concurrent reads of the mutable configs and nested repo dictionaries against createRepo/getRepo writes.\n\n## Validation\n- \git diff --check\ passed.\n- Native Database tests were not run because Xcode is unavailable in this environment.\n- clang-format was unavailable in PATH.

@gemini-code-assist

Copy link
Copy Markdown
Contributor
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

@paulb777

paulb777 commented Oct 1, 2026

Copy link
Copy Markdown
Member

Thanks for the contribution! A couple of housekeeping items:

  • Formatting: please run scripts/style.sh so the infra.check job passes. It needs clang-format 23 and swiftformat (see scripts/setup_check.sh). If you can't run it locally, the infra.check log lists the files that need formatting.
  • CHANGELOG (optional): if you add an entry for this fix, put it under a # Unreleased heading at the top of FirebaseDatabase/CHANGELOG.md and end it with this PR's number, e.g. - [fixed] Description. (#16774).

@paulb777 paulb777 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, this finishes applying the @synchronized(configs) locking that createRepo and getRepo already use. interruptAll/resumeAll (reachable from goOffline()/goOnline()) and disposeRepos previously read or mutated configs without the lock. Looks good to me apart from a nit and the formatting.

+ (NSArray<FRepo *> *)reposForConfigIdentifier:(NSString *)sessionIdentifier
inConfigs:(FRepoDictionary *)configs {
@synchronized(configs) {
return [[configs[sessionIdentifier] allValues] copy] ?: @[];

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: allValues already returns a new array, so the copy isn't needed (same at L50).

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants