-
Notifications
You must be signed in to change notification settings - Fork 28
Fix: Implement deterministic file naming to prevent storage leak #447
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
Open
vibhutomer
wants to merge
1
commit into
PSMRI:main
Choose a base branch
from
vibhutomer:fix/storage-leak-deterministic-names
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
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
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
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
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.
Edge case: nullable
item.idproduces collision-prone filename.UwinServerItem.idisInt?(line 271). Whenidis null, the filename becomesuwin_null_img0.$ext, so multiple server entries lacking an id will overwrite each other's cached images on the same down-sync. Either skip the item early or substitute a stable fallback before building the file name.π Proposed fix
val localList = entries.mapNotNull { item -> + val itemId = item.id ?: return@mapNotNull null val imageUriList = item.meetingImages?.mapIndexedNotNull { index, base64 -> try { val base64Data = base64.substringAfter(",", base64) val bytes = Base64.decode(base64Data, Base64.DEFAULT) val (ext, _) = detectExtAndMime(bytes) - val file = File(appContext.cacheDir, "uwin_${item.id}_img${index}.$ext") + val file = File(appContext.cacheDir, "uwin_${itemId}_img${index}.$ext")π€ Prompt for AI Agents