-
Notifications
You must be signed in to change notification settings - Fork 1.5k
[PM-11249] Update cipher revision date when an attachment is added or deleted #4873
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
Conversation
|
❓ Are you still able to modify the cipher after uploading an attachment? I'm worried that we don't return the updated cipher in the attachment endpoint so the |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #4873 +/- ##
==========================================
- Coverage 44.32% 44.31% -0.01%
==========================================
Files 1482 1483 +1
Lines 68376 68388 +12
Branches 6172 6172
==========================================
Hits 30307 30307
- Misses 36761 36773 +12
Partials 1308 1308 ☔ View full report in Codecov by Sentry. |
Nice catch, I only tested on the client that received the update which in turn would have the updated cipher. On the same client you are not able to. 🤔 Screen.Recording.2024-10-09.at.1.32.52.PM.mov |
|
New Issues (12)Checkmarx found the following issues in this Pull Request
Fixed Issues (28)Great job! The following issues were fixed in this Pull Request
|
|
Marking this a draft as I have yet to track down all of the necessary changes on server and client side. Priorities have changed so I'll be taking up some other work in the mean time. See the ticket for more details about solutioning these scenarios. |
…/pm-11249/attachment-cipher-date
…/pm-11249/attachment-cipher-date
…/pm-11249/attachment-cipher-date
…/pm-11249/attachment-cipher-date
|
@shane-melton I order to support this change for deleting an attachment, the UI needed to know the updated revision timestamp. I added logic to return the updated cipher to both the client and here 13acab5 |
gbubemismith
left a comment
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.
Changes look good
…/pm-11249/attachment-cipher-date
…/pm-11249/attachment-cipher-date
|
Moving to a draft as this work is being tabled for a couple weeks why we wait for the extension refresh to roll out. |
…/pm-11249/attachment-cipher-date



🎟️ Tracking
PM-11249
📔 Objective
Current Issue: When an attachment is added or deleted, web/browser clients are not being updated of the change.
Cause: The logic within the CoreSyncService on the client side uses the cipher revision date to determine if a sync is needed. Server side the cipher revision date isn't updated.
Proposed Fix:
📸 Screenshots
attachments-before.mov
attachments-after.mov
🦮 Reviewer guidelines
:+1:) or similar for great changes:memo:) or ℹ️ (:information_source:) for notes or general info:question:) for questions:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion:art:) for suggestions / improvements:x:) or:warning:) for more significant problems or concerns needing attention:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt:pick:) for minor or nitpick changes