processing / processing/p5.js-web-editor

Assets Not Removed from AWS S3 on Sketch Deletion

Open
#3,754 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Bug Needs Steps to Reproduce
Dominant language
JavaScript
Stars
1.7k
Forks
1.7k
Avg merge
3d 4h
Merged PRs (30d)
8

Description

p5.js version

No response

What is your operating system?

None

Web browser and version

No response

Actual Behavior

Reported by email:

A few days ago, a user reaching out to delete their account noticed that despite deleting all of the sketches and assets from their account, the asset storage bar still indicated used storage space (pictured in partial screenshot below).

Screenshot of empty Asset list but 57% storage used.

After taking a look on AWS S3, it seems like the user still had assets associated with their account, but had no sketches on MongoDB.

Expected Behavior

When a sketch is deleted, the storage bar in the Assets tab should update accordingly.

Steps to reproduce

I wasn't able to reproduce it consistently yet—thoughts on this would be helpful!

I was able to encounter this issue once through the following steps:

  1. Creating a new sketch.
  2. Uploading an asset to the sketch, then saving the sketch.
  3. Going to 'My Sketches' and confirming that the sketch is saved in the 'Sketches' tab and that the asset exists in the 'Assets' tab.
  4. Deleting the sketch through the dropdown icon in the 'Sketches' tab.
  5. Going back to the Assets tab, which did not reflect a change in the storage size amount.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the sketch deletion flow from the Sketches tab and checking how its assets are removed from AWS S3 and represented in MongoDB. Reproduce the listed create, upload, save, and delete steps, then verify that the Assets tab storage value updates and no orphaned assets remain.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, javascript, mongodb
Domain
backend, cloud, databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.