Follow-up: Very slow JSON:API responses when images are stored on AWS bucket

Created on 2 August 2022, over 2 years ago
Updated 7 February 2023, almost 2 years ago

I still experience the issues as mentioned in #3252023: Very slow JSON:API responses when images are stored on AWS bucket β†’ .

The problem is the call to $image = $this->imageFactory->get($uri);

AFAICS, this was fixed for ImageStylesProvider::buildDerivativeLink() but not for LinkCollectionNormalizer::buildVariantLinks(), am I right?

πŸ› Bug report
Status

Needs review

Version

4.0

Component

Code

Created by

πŸ‡©πŸ‡ͺGermany osopolar πŸ‡©πŸ‡ͺ GER 🌐

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡©πŸ‡ͺGermany osopolar πŸ‡©πŸ‡ͺ GER 🌐
  • Status changed to RTBC almost 2 years ago
  • πŸ‡ΊπŸ‡ΈUnited States apmsooner

    patch in #9 is working for me. Prior to applying this patch, the jsonapi route for files was failing and logging errors for property validation:

    Errors: [
      {
        "property": "",
        "pointer": "",
        "message": "The property data is not defined and the definition does not allow additional properties",
        "constraint": "additionalProp",
        "context": 1
      },
      {
        "property": "data",
        "pointer": "\/data",
        "message": "Array value found, but a null is required",
        "constraint": "type",
        "context": 1
      },
      {
        "property": "data",
        "pointer": "\/data",
        "message": "Array value found, but an object is required",
        "constraint": "type",
        "context": 1
      },
      {
        "property": "data[1].links.placeholder.href",
        "pointer": "\/data\/1\/links\/placeholder\/href",
        "message": "Invalid URL format",
        "constraint": "format",
        "context": 1,
        "format": "uri-reference"
      },
      {
        "property": "data[1].links.placeholder",
        "pointer": "\/data\/1\/links\/placeholder",
        "message": "Object value found, but a string is required",
        "constraint": "type",
        "context": 1
      },
      {
        "property": "data[1].links.placeholder",
        "pointer": "\/data\/1\/links\/placeholder",
        "message": "Failed to match exactly one schema",
        "constraint": "oneOf",
        "context": 1
      },
      {
        "property": "data",
        "pointer": "\/data",
        "message": "Failed to match exactly one schema",
        "constraint": "oneOf",
        "context": 1
      },
      {
        "property": "errors",
        "pointer": "\/errors",
        "message": "The property errors is required",
        "constraint": "required",
        "context": 1
      },
      {
        "property": "",
        "pointer": "",
        "message": "Failed to match exactly one schema",
        "constraint": "oneOf",
        "context": 1
      }
    ]
    
  • πŸ‡¨πŸ‡ΏCzech Republic mkolar

    Hi! patch #9 works for me, before patch we had problem with API exactly like @apmsooner. RTBC! TY!

    also thanks @apmsooner for posting that error here, we found this patch thanks to it!

  • πŸ‡ΊπŸ‡ΈUnited States tjh

    Patch #9 works for me as well. We were also experiencing schema validation errors as described in #10

  • First commit to issue fork.
  • Pipeline finished with Skipped
    3 months ago
    #306370
  • πŸ‡ΊπŸ‡ΈUnited States japerry KVUO
  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.71.5 2024