Skip to content

Conversation

@paulb777
Copy link
Member

Fix #4493

@gemini-code-assist
Copy link
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

Customization

To customize 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 counter productive. 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
Copy link
Member Author

/gemini review

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request addresses a FirebaseDatabasePersistenceFailure fatal exception by setting appropriate file protection attributes when creating the persistence directory. This change allows directory creation even when the device is locked. Additionally, the error reporting is improved by including the underlying NSError in the thrown exception, and the logic is made more robust by logging a warning instead of crashing if setting the 'do not backup' attribute fails. A new unit test has been added to verify the correct file protection attribute is set. The changes are well-implemented and address the issue effectively. I have one minor suggestion to enhance code safety.

@paulb777 paulb777 closed this Nov 30, 2025
@paulb777 paulb777 force-pushed the pb-rtdb-file-protection branch from 8e29812 to f63f3cc Compare November 30, 2025 18:17
@paulb777 paulb777 reopened this Nov 30, 2025
Copy link
Member

@ncooke3 ncooke3 Dec 1, 2025

Choose a reason for hiding this comment

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

When the directory already exists, it doesn't sound like the file protection attribute will be updated: true if createIntermediates is set and the directory already exists (from docs).

To handle this case, I think we need to instead set the attribute via this API: https://developer.apple.com/documentation/foundation/filemanager/setattributes(_:ofitematpath:)?language=objc

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Fatal Exception: FirebaseDatabasePersistenceFailure

3 participants