Building static HTML for pageserror: Error: ENOENT: no such file or directory

[hackhat]

Description

I'm getting a lot of similar errors to this:

 success Building production JavaScript and CSS bundles — 8.258 s
 ⠐ Building static HTML for pageserror ../public/29/path---internal-80-aeac-04-012-a-4-feb-9-d-99-d- 
   6053-a-12-be-5-a-r-006-91-c-794-olfyUiQvtLIAh9ozYkUiFQEB1M
 { Error: ENOENT: no such file or directory, open' X:\xxx\xxx\public\static\d\29\path---internal-80-aeac-04-012-a-4-feb-9-d-99-d-6053-a-12-be-5-a-r-006-91-c-794-olfyUiQvtLIAh9ozYkUiFQEB1M.json'

and then hangs with " Building static HTML for pages" for long time.

Steps to reproduce

Don't know... Just deleted the public folder and build it.

Environment

Run gatsby info --clipboard in your project directory and paste the output here. Not working? You may need to update your global gatsby-cli - npm install -g gatsby-cli

System:
OS: Windows 10
CPU: x64 Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz
Binaries:
Yarn: 1.9.4 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
npm: 5.5.1 - C:\Program Files\nodejs\npm.CMD
Browsers:
Edge: 42.17134.1.0
npmPackages:
gatsby: ^2.0.67 => 2.0.67
gatsby-image: ^2.0.25 => 2.0.25
gatsby-plugin-catch-links: ^2.0.9 => 2.0.9
gatsby-plugin-emotion: ^3.0.1 => 3.0.1
gatsby-plugin-google-analytics: ^2.0.8 => 2.0.8
gatsby-plugin-manifest: ^2.0.12 => 2.0.12
gatsby-plugin-offline: ^2.0.19 => 2.0.19
gatsby-plugin-react-helmet: ^3.0.0 => 3.0.0
gatsby-plugin-sharp: ^2.0.15 => 2.0.15
gatsby-plugin-sitemap: ^2.0.3 => 2.0.3
gatsby-plugin-typescript: ^2.0.3 => 2.0.3
gatsby-plugin-typography: ^2.2.2 => 2.2.2
gatsby-remark-component: ^1.1.3 => 1.1.3
gatsby-remark-images: ^3.0.1 => 3.0.1
gatsby-source-filesystem: ^2.0.12 => 2.0.12
gatsby-transformer-remark: ^2.1.15 => 2.1.15
gatsby-transformer-sharp: ^2.1.9 => 2.1.9

[hackhat]

Ok, so I had this issue: #10458 I run gatsby develop a few times and now it works. Then I build and it works.. what is going on? I need to run gatsby develop before building?

[hackhat]

I deleted my public folder and build again, same error again.

I deleted cache folder and build and now it worked.

[DSchau]

Hello!

Sorry about the issues! Could you provide a reproduction or something we could take a look at? Thanks!

[hackhat]

I can't... is just in my project and I don't have a clue about what is affecting this. It's incredibly flaky.

[DSchau]

If it's something that happens every X times, e.g. every ~5 times or something, and you can reproduce it occasionally that's still more to go on that we have now.

It's pretty challenging to know how to begin debugging this. At first glance, it could be some type of Windows pathing issue, but that's a shot in the dark at this point.

Thanks!

[hackhat]

If I run gatsby start and then run gatsby build it fails. If I delete the cache folder and run gatsby build it works.

[DSchau]

That's enough for us to go on! Is it possible to share the repository (or create a minified example without any private info) so we could take a look ourselves?

[hackhat]

I can't right now, is pretty big and entangled... What can we do?

[pieh]

We do output query results to public directory directly, but we keep track of them in .cache - so if you delete public without deleting .cache - cache won't know that query results are no longer there and that's why we it complains about missing file that cache expects to be there

[hackhat]

@pieh Looks like it's correct. So probably we should do something to avoid this scenario. Maybe put an error that in order to build without public folder you need to delete the .cache folder as well.

But I found it strange for the .cache to look into the public folder... but anyway, that's something else.

[pieh]

But I found it strange for the .cache to look into the public folder... but anyway, that's something else.

So this is kind of to eliminate some of the "unnecessary" work - like if we output query results to .cache we would need to copy them later on to public anyway. But for sure it comes with issues like that. We definitely could/should check if query results are available and rerun queries if they are not

[jonniebigodes]

@hackhat this a bit of a edge case, normally people don't even touch these folders, or if they do they delete both of them, either by using a script, or using an auxiliary package to handle that situation.
And controlling the scenario you mentioned could be a bit tricky, as both folders are automatically generated, if not present they are generated and their content filled by gatsby and if they are gatsby goes about it's business, starts incrementally making the checks needed and updating the contents incrementally. And if everything is working properly you get an ok, or like it happened to you it throws an error.
I believe that this should be a case to be handled by the actual developer, not the tool itself. Before issuing production build and/or issuing the development command you should do some "house cleaning" (pardon the bad pun) beforehand and always getting the correct/actual data/contents you have. And i might be completely off on this, and feel free to correct me, but it's a defensive strategy i adopted that's been working for me since i've discovered gatsby in the past year.

[sidharthachatterjee]

We can maybe add a gatsby clean to the cli that deletes both the folders but generally, @jonniebigodes makes a good point that these folders ought not to be touched since they are owned by gatsby .

Apologies for the not very helpful error messages. We are working towards improving this.