-
Notifications
You must be signed in to change notification settings - Fork 5
chore: make blabsy admin auth more robust #421
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
Merged
Merged
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
2 changes: 1 addition & 1 deletion
2
infrastructure/eid-wallet/src-tauri/gen/android/.idea/kotlinc.xml
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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
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.
🧩 Analysis chain
Verify impact on webhook and watcher features when Firebase is not initialized.
The warning correctly identifies potential failures in webhook and watcher features. Ensure that these features handle the uninitialized state gracefully without crashing or exposing error details to clients.
Run the following script to check how webhook and watcher features handle Firebase dependencies:
🏁 Script executed:
Length of output: 1578
🏁 Script executed:
Length of output: 10982
🏁 Script executed:
Length of output: 2372
Add error handling for Firebase dependencies in WebhookController and Web3Adapter instantiation.
The warning at lines 88-90 is correct but incomplete. Both
WebhookController(line 102) andWeb3Adapter(line 93) will crash during instantiation if Firebase is not initialized, because their constructors callgetFirestore()without guards:WebhookControllerconstructor (line 84):this.db = getFirestore()Web3Adapterclass property (line 17):private readonly db = getFirestore()FirestoreWatcherconstructor (line 49):this.db = getFirestore()These instantiations lack try-catch wrappers. The app will crash with an unhandled error instead of gracefully degrading. Either wrap instantiations in try-catch blocks or add guards to prevent
getFirestore()calls when Firebase is uninitialized.🤖 Prompt for AI Agents