-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
3.0.2 breaks uploader behavior with rollback and deletes files in remote #2685
Comments
I'm trying to create a failing test case right now. |
rajyan
pushed a commit
to rajyan/carrierwave
that referenced
this issue
Aug 17, 2023
files should not be removed on rollback if not updated
rajyan
pushed a commit
to rajyan/carrierwave
that referenced
this issue
Aug 17, 2023
files should not be removed on rollback if not updated
Done. #2686 |
Could you please cut a new release? |
You're right, just released 3.0.3. |
Thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
From 3.0.2, carrierwave started to delete files in remote when rollback happens. (which causes a 404 link)
I haven't found the root cause yet, but confirmed that it doesn't happen in 3.0.1.
Still looking for the cause in
#2679
sample code
post model has a has_many association with attachment model, which mounts a uploader.
when the transaction is rolled back by
find
orsave!
, file is deleted for attachment that is saved in the previous iteration.The text was updated successfully, but these errors were encountered: