Orphaned Assets Fix#4119
Conversation
|
Hi Yugal! Thanks so much for the PR! Apologies for the delay, will take a look this upcoming week. |
|
@khanniie Reminder for review 👩🏼💻 |
|
actually if @raclim is back maybe she would be a better reviewer for this one? I don't have much context on the backend side of the editor to be honest |
|
@raclim Hi, I have updated the logic to use a better approach, please review the PR. |
|
hi @yugalkaushik! i noticed two related issues:
combining these two issues means there is currently no way for a user to delete uploaded assets from an unsaved sketch (both issues are still present in this release). |
|
@skyash-dev thank you for the review, I'll fix these in coming days. |
raclim
left a comment
There was a problem hiding this comment.
Thanks so much for your work on this @yugalkaushik! Sorry that it took a while to review!
I think it looks okay to me so far so I'm going to merge this in, but definitely open to any further testing over the next few days before release next Tuesday!
|
Wait sorry @yugalkaushik! Could you provide a screenshot or specify the configurations for the S3 lifecyle rule? |
|
Hi @raclim Here is the exact screenshots for the lifestyle rule. |
|
Awesome! This is super helpful, thanks so much! |



Issue:
Completes #4107
This change adds a pending-upload workflow for user assets so files are not permanently stored until a project is successfully saved. It also adds rollback for failed clones and a scheduled cleanup path for abandoned pending uploads. Uploaded assets now go to a pending S3 prefix first, are committed into the final user/project location on save, and are removed later if they stay pending too long. The cleanup threshold is 7 days.
Demo:
preview-orphanedassets.mp4
Changes:
I have verified that this pull request:
npm run lint)npm run test)npm run typecheck)developbranch.Fixes #123