ERROR #85901 GRAPHQL : Unexpected error value: "failed to process

[KamranMaqbool]

"gatsby develop"
not download .png image file

give me error

tihis same error on some other pages

My GraphQL Query like this
query GET_PAGE($id: ID!) { wpgraphql { page(id: $id) { id pageId uri title content featuredImage { sourceUrl altText imageFile { childImageSharp { fluid(maxWidth: 1200, maxHeight:600, quality: 80, cropFocus: CENTER) { ...GatsbyImageSharpFluid_withWebp_noBase64 } } } } } }

Wordpress GraphQL Query

Gatsby GraphQL Query

before above query work file but now it's give me error when click on imageFile node like below

imageFile {} object only show in gatsbyjs wpgraphQL but why not show in WPGraphQL Query.i don't understand what this happen
some days ago this working perfect

Environment

Ubuntu OS
"gatsby": "^2.24.50",
"gatsby-image": "^2.4.16",
"gatsby-plugin-sharp": "^2.6.28",
"gatsby-source-graphql": "^2.7.2",
"gatsby-transformer-sharp": "^2.5.13",

[MKlblangenois]

I've the same issue, process return error when he's trying to download PNG file

Processing /Users/loganblangenois/Documents/Sites/Gatsby/Clients/gatsby-studyfr-v5/.cache/caches/gatsby-source-wordpress-experimental/a1aa62e5163bc8656a334d10837722b0/Warmadewa University Logo.png failed

Original error:

  WorkerError: Processing /Users/loganblangenois/Documents/Sites/Gatsby/Clients/gatsby-studyfr-v5/.cache/caches/gatsby-source-wordpress-experimental/a1aa62e5163bc8656a334d10837722b0/  Warmadewa University Logo.png failed
  Original error:
  
  - jobs-manager.ts:318 enqueueJob
    [gatsby-studyfr-v5]/[gatsby]/src/utils/jobs-manager.ts:318:21
  
  - runMicrotasks
  
  - task_queues.js:97 processTicksAndRejections
    internal/process/task_queues.js:97:5

• "gatsby": "^2.24.50",
• "gatsby-image": "^2.4.16",
• "gatsby-plugin-sharp": "^2.6.28",
• "gatsby-source-wordpress-experimental": "^1.3.8",
• "gatsby-transformer-sharp": "^2.5.13",

[pieh]

@KamranMaqbool The 409 (Conflict) error comes from wordpress server in this is root problem here. It might be combination of the way file is being downloaded. Some brief info on 409 - https://httpstatuses.com/409

Does the error happen consistently? If so - try clearing gatsby cache (gatsby clean command) and try build/develop again - this might be some weirdness with our downloader trying to use ETAG which maybe is not supported by your server in weird way?

imageFile {} object only show in gatsbyjs wpgraphQL but why not show in WPGraphQL Query.i don't understand what this happen

I see you are using wpgraphql with gatsby-source-graphql combination, which means that you probably also use something like https://gist.github.com/henrikwirth/4ba900b7f89b9e28ec81497466b12710 to add this custom field in Gatsby GraphQL layer (which is why this is only available in gatsby and not on WPGraphQL)

[pieh]

@MKlblangenois your issue doesn't seem related. This is about image processing, so I would suggest either finding similar issue or opening new one if there were no reports for it yet.

[theskillwithin]

I am getting same issues as @MKlblangenois on a random single png file. I upgrade about every week so I think recent.

[KamranMaqbool]

@pieh
I'm also try to remove node_modules & (gatsby clean command)
but same error occurs

[KamranMaqbool]

@pieh
this error produce in local environment
when deploy in production(on Netlify) no error occur.it's working fine

[linoxyn]

I'm getting a similar error in development. Errors out even when I remove or replace the image it fails on.

Processing C:/Projects/lochwebsite/.cache/caches/gatsby-source-google-docs/40ddb3df04d7c5a8a0473e6bf801d4b2/google-docs-image-4d7218b8-316a-5853-aab9-4663599dcda2.png failed

Original error:

  WorkerError: Processing C:/Projects/lochwebsite/.cache/caches/gatsby-source-google-docs/40ddb3df04d7c5a8a0473e6bf801d4b  2/google-docs-image-4d7218b8-316a-5853-aab9-4663599dcda2.png failed
  Original error:

  - jobs-manager.ts:318 enqueueJob
    [lochwebsite]/[gatsby]/src/utils/jobs-manager.ts:318:21

  - runMicrotasks

  - task_queues.js:97 processTicksAndRejections
    internal/process/task_queues.js:97:5

not finished Generating image thumbnails - 140.317s

Initially I thought this might have been an issue with gatsby-source-google-docs as this is the CMS I'm using to download images from Google Docs. I have been trying to find a working development setup where I can get all the images generated without error and I found if I set an older gatsby-plugin-sharp@2.6.29 version it works.

Partial list of packages:

• "gatsby": "^2.24.54",
  

• "gatsby-cli": "^2.12.92",
  

• "gatsby-image": "^2.4.17",
  

• "gatsby-plugin-catch-links": "^2.3.11",
  

• "gatsby-plugin-manifest": "^2.4.28",
  

• "gatsby-plugin-offline": "^3.2.27",
  

• "gatsby-plugin-prefetch-google-fonts": "^1.4.3",
  

• "gatsby-plugin-react-helmet": "^3.3.10",
  

• "gatsby-plugin-sharp": "^2.6.29",
  

• "gatsby-plugin-styled-components": "^3.3.10",
  

• "gatsby-plugin-typography": "^2.5.10",
  

• "gatsby-remark-embed-video": "^3.0.10",
  

• "gatsby-remark-images": "^3.3.29",
  

• "gatsby-remark-responsive-iframe": "^2.4.13",
  

• "gatsby-source-filesystem": "^2.3.28",
  

• "gatsby-source-google-docs": "^2.0.0-beta.18",
  

• "gatsby-transformer-remark": "^2.8.33",
  

• "gatsby-transformer-sharp": "^2.5.14",
  

[MKlblangenois]

imagemin-pngquant just merge PR's #71 (imagemin/imagemin-pngquant#71) that solve the issue. Just update or install imagemin-pngquant@9.0.1 fix error on local and Netlify

[github-actions]

Hiya!

This issue has gone quiet. Spooky quiet. 👻

We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 20 days since the last update here.
If we missed this issue or if you want to keep it open, please reply here.
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks for being a part of the Gatsby community! 💪💜

[github-actions]

Hey again!

It’s been 60 days since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it.
Please keep in mind that I’m only a robot, so if I’ve closed this issue in error, I’m HUMAN_EMOTION_SORRY. Please feel free to comment on this issue or create a new one if you need anything else.
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks again for being part of the Gatsby community! 💪💜