fix(plugin-cloud-storage): propagate user afterChange hook errors during upload#16592
Open
jacobsfletch wants to merge 2 commits into
Open
fix(plugin-cloud-storage): propagate user afterChange hook errors during upload#16592jacobsfletch wants to merge 2 commits into
jacobsfletch wants to merge 2 commits into
Conversation
Contributor
📦 esbuild Bundle Analysis for payloadThis analysis was generated by esbuild-bundle-analyzer. 🤖
Largest pathsThese visualization shows top 20 largest paths in the bundle.Meta file: packages/next/meta_index.json, Out file: esbuild/index.js
Meta file: packages/payload/meta_index.json, Out file: esbuild/index.js
Meta file: packages/payload/meta_shared.json, Out file: esbuild/exports/shared.js
Meta file: packages/richtext-lexical/meta_client.json, Out file: esbuild/exports/client_optimized/index.js
Meta file: packages/ui/meta_client.json, Out file: esbuild/exports/client_optimized/index.js
Meta file: packages/ui/meta_shared.json, Out file: esbuild/exports/shared_optimized/index.js
DetailsNext to the size is how much the size has increased or decreased compared with the base branch of this PR.
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes #16573.
When a collection using
@payloadcms/plugin-cloud-storagehas a user-definedafterChangehook that throws an error, the plugin swallows the error, logging it as awarn. Payload silently rolls back the changes, leaving S3 and the database in inconsistent states without notifying the user that an error has occurred.Problem
Two problems in the plugin's
afterChangehandler:req.payload.update()was wrapped in atry/catchthat only emittedlogger.warn. Anything thrown downstream — including a user's ownafterChangehook — was swallowed, so the outer operation completed "successfully" while its side effects were broken.Solution
try/catcharound the inner update. The outertry/catchin the same hook already logs and re-throws, so errors now surface to the caller and the admin UI.skipCloudStoragecontext flag intry/finallyso it is always cleared, even when the inner update throws.Now, user errors are surfaced to the caller, the previous file stays in S3, and the document keeps pointing at a valid object.