[REQUIRED] Step 2: Describe your configuration
- Extension name: storage-resize-images
- Extension version: 0.3.2
- Configuration values (redact info where appropriate):
- Cloud Storage path for failed images:
failed
- Content filter level:
High strictness
- Path to placeholder image:
placeholder/blocked-content.png
- Deletion of original file:
Delete on any resize attempt (Bug happens with 'Keep' as well)
- Convert image to preferred types:
webp
[REQUIRED] Step 3: Describe the problem
Steps to reproduce:
- Install the
storage-resize-images extension with Content Filtering enabled (Vertex AI API enabled).
- Configure a valid path for
Cloud Storage path for failed images (e.g., failed).
- Configure a custom placeholder image.
- Upload an image that triggers the content filter (e.g., inappropriate content).
- Review the Storage bucket and the Cloud Function logs.
Expected result
According to the official documentation:
"If you’ve configured a failed images path, the original image is moved to that location with metadata indicating it was blocked by content filtering."
The expected behavior is that the extension generates the resized placeholder versions AND moves the original malicious image to the failed path, adding the rejection metadata.
Actual result
The extension successfully detects the inappropriate content and successfully generates the resized placeholder images (e.g., _200x200.webp, _600x600.webp). However, the original blocked image is NEVER moved to the failed images path, nor is any metadata applied to it.
Technical context (Why this is happening):
Looking at the Cloud Function logs, when Vertex AI blocks the content, the extension successfully swaps the image buffer with the placeholder buffer and completes the resizing process. Because this placeholder replacement is successful, the function finishes with status: 'ok'.
It appears the logic to move the original file to the failed path and apply rejection metadata is currently placed inside an error handling block (catch). Since the placeholder generation prevents the function from throwing an error, the catch block is completely bypassed, leaving the original blocked image in its source directory.
Log sequence observed:
Replacing filtered image with configured placeholder...Image content blocked by Vertex AI content filters.Successfully replaced filtered image with placeholder...Resizing image at path...Function execution took X ms, finished with status: 'ok'
(Missing: Any log indicating "Moving original file to failed path")
[REQUIRED] Step 2: Describe your configuration
failedHigh strictnessplaceholder/blocked-content.pngDelete on any resize attempt(Bug happens with 'Keep' as well)webp[REQUIRED] Step 3: Describe the problem
Steps to reproduce:
storage-resize-imagesextension with Content Filtering enabled (Vertex AI API enabled).Cloud Storage path for failed images(e.g.,failed).Expected result
According to the official documentation:
The expected behavior is that the extension generates the resized placeholder versions AND moves the original malicious image to the
failedpath, adding the rejection metadata.Actual result
The extension successfully detects the inappropriate content and successfully generates the resized placeholder images (e.g.,
_200x200.webp,_600x600.webp). However, the original blocked image is NEVER moved to the failed images path, nor is any metadata applied to it.Technical context (Why this is happening):
Looking at the Cloud Function logs, when Vertex AI blocks the content, the extension successfully swaps the image buffer with the placeholder buffer and completes the resizing process. Because this placeholder replacement is successful, the function finishes with
status: 'ok'.It appears the logic to move the original file to the
failedpath and apply rejection metadata is currently placed inside an error handling block (catch). Since the placeholder generation prevents the function from throwing an error, thecatchblock is completely bypassed, leaving the original blocked image in its source directory.Log sequence observed:
Replacing filtered image with configured placeholder...Image content blocked by Vertex AI content filters.Successfully replaced filtered image with placeholder...Resizing image at path...Function execution took X ms, finished with status: 'ok'(Missing: Any log indicating "Moving original file to failed path")