Unable to build because of an image fetching / caching error

[sreucherand]

Hello!

I'm experiencing a bug using this plugin. Seems to be related to the image caching process.
It happens when building. But only after having cleaned the cache when developing (it works on second run). First yarn start fails then yarn start again and it works.

Here is the error that I'm getting:

ERROR #85901  GRAPHQL

There was an error in your GraphQL query:

Unexpected error value: "failed to process https://images.prismic.io/issue-03152020/59a58991-59d6-4846-8a67-4306459d5248_original.jpg?auto=compress,format&rect=0,0,1820,2275&w=1820&h=2275\nError: ENOENT: no such file or directory, open '/Users/*****/issue-03152020/.cache/caches/gatsby-source-prismic-graphql/tmp-c09596de258a31bc721c83493efba974.jpg'"

I replicated the bug on a fresh install for you to reproduce: https://github.com/sreucherand/issue-03152020

[andyto]

I am suspecting something is wrong on Prismic's end. I tried to republish the assets in Primsic and it managed to get past occasionally.

[andyto]

I discovered that as long as there is the folder .cache/caches/gatsby-source-prismic-graphql, there will be no error. When the folder is not present, it seems to have a problem creating this folder, thus the above error will happen. It can be solved by creating the folder manually.

In a local development environment, we can create the folder manually, but would be impossible when deployed in netlify for example. Hope this will be fixed soon.

[dphoursa]

@andyto You can create the folder on the fly by placing the following code in gatsby-node.js (this will work for netlify):

var fs = require('fs');
var dir = "./.cache/caches/gatsby-source-prismic-graphql"

exports.onPreBootstrap = () => {
    if (!fs.existsSync(dir)){
        fs.mkdirSync(dir);
    } 
 }

[sreucherand]

Good catch all!
I found a working fix actually. In gatsby-node.ts, createResolvers should be passing its argument getCache along to createRemoteFileNode as such:

exports.createResolvers = ({ cache, getCache, [...] }) => {
  [...]
  return createRemoteFileNode({
    [...],
    cache,
    getCache,
    [...]
  });
}

I have not investigated more on this. Might do it later and follow up with a PR.

createRemoteFileNode ts types have been updated in version 2.1.55 to allow getCache (see. gatsbyjs/gatsby#22090)

[elias-thok]

I have the same issue. Cost me hours and hours.
Also, if I strip all the imageSharp parts off the graphql-query, the build works and creates .cache/caches/gatsby-source-prismic-graphql. If I then add the imageSharp parts again, the build works, until the next gatsby clean.

@dphoursa your hack works but I hope that's only temporary.

Edit:
Also, I'm having random graphql errors while I run gatsby develop. Sometimes the site crashes with some imageSharp fragments being undefined all of a sudden, even if no image-related code has been changed. Restarting the process often gets rid of it. Could that be related in any way?

[dphoursa]

@elias-thok Very strange. Are you following the new plugin config of the latest release. Is the name of your image attribute in prismic matches sharpKeys?

[Jdruwe]

I have the same issue. Unexpected error value: "failed to process https://images.prismic.io/jeroendruwe/cced738b-fa9f-4b84-9d5f-4b4a03ce42f7_frituur.png?auto=compress,format\nError: ENOENT: no such file or directory, open '/Users/jdruwe/Work/freelance/jeroendruwe/.cache/caches/gatsby-source-prismic-graphql/tmp-32ccaf04c2df563b22d46b86a5621c90.png'" Due to imageSharp { in my query

[madeleineostoja]

Just wanted to chime in to say that I can confirm this is a regression in the latest version of the source — I have 2 projects where I changed nothing but upgraded this package and saw this error. The monkeypatch from @dphoursa works well for now.

[codingwithchris]

I have the exact same issue as described by multiple others above. When trying to query any Sharp image field without an existing ./.cache/caches/gatsby-source-prismic-graphql directory, I get an error similar to:

UNHANDLED REJECTION ENOENT: no such file or directory, open '${mypath}/.cache/caches/gatsby-source-prismic-graphql/${queriedImage}.jpg'

I can also confirm that the on-the-fly folder creation patch in gatsby-node.js suggested above by @dphoursa is working for me. Hoping we can get this fixed for real soon. 🤞

[laradevitt]

Also ran into this problem. Confirming either rolling back to 3.4.1-alpha.0 or using above-mentioned workaround in gatsby-node.js resolves the error for now. Thanks!

[ptrkvsky]

var fs = require("fs")
var dir = "./.cache/caches/gatsby-source-prismic-graphql"

exports.onPreBootstrap = () => {
  if (!fs.existsSync(dir)) {
    fs.mkdirSync(dir)
  }
}

Wordked for me thanks