datocms/gatsby-source-datocms

Time out Build

Pierregadait opened this issue · 19 comments

Hello,

We are facing blocking issue with major business impact on our website: [https://ikeys-realty.com/en]
After reaching Gatsby support, they tell us that the call stack error is coming from gatsby-source-datocms which they do not maintain.

Context:
We have a timeout issue when building. Please find a screenshot of our issue :
unnamed

Our previous actions:

  1. Verified the domain
  2. Remove cloudflare proxy on all the subdomains (it was proxied for some reason)
  3. Updated the IP Addresses (@ were going to an old IP on your side ?)
    We also did a rebuild of the preview (there was a prompt for us to do that in gatsby).

However, like for the previous builds, it time outed at some point (screenshot)

  • We have a feeling this is happening when it's trying to regenerate the permalinks ?
  • Is there a way to see whether stuff sent by Dato actually ends up in gatsby ?

Sending stuff randomly I'm seeing as marked as published from https://admin.ikeys-realty.com/ , but whose slugs are / are not working:

[working]

  1. https://ikeys-realty.com/en/19575-collins-ave-38
  2. https://ikeys-realty.com/en/villa-rosetti
  3. https://ikeys-realty.com/en/334-atlantic-ave

[not working]

  1. https://preview-ikeys.gtsb.io/for-sale-4-bedroom-luxury-penthouse-with-panoramic-view-on-the-marina-and-the-bla
  2. https://preview-ikeys.gtsb.io/epic-apartment-designed-by-the-prestigious-fendi-casa
  3. https://preview-ikeys.gtsb.io/gorgeous-villa-in-algarve-in-portugal
  4. https://preview-ikeys.gtsb.io/incredible-villa-in-algarve-in-portugal

FYI, the working ones, are not working in preview, so ( with and without /en/ which is also. a difference between the preview engine and the live engine ):

  1. https://ikeys-realty.com/en/19575-collins-ave-38 ( doesn't work in https://preview-ikeys.gtsb.io/en/19575-collins-ave-38 )
  2. https://ikeys-realty.com/en/villa-rosetti ( doesn't work in https://preview-ikeys.gtsb.io/en/villa-rosetti )
  3. https://ikeys-realty.com/en/334-atlantic-ave ( doesn't work in https://preview-ikeys.gtsb.io/334-atlantic-ave )

Which makes us believe either :

  1. Dato isn't sending stuff properly ( or at all ) to gatsby
  2. Data gets sent, something in gatsby ( what ? ) is preventing slugs from working properly

Maybe the samples above will help you find out what's different from the working / not working permalinks?

First of all I am not working for DatoCMS. I also got error for my secondary locale after updating react and react-dom to v18.0.0. I am not sure if we have the similar problem. I am not sure if I should open another issue or we are on the same page.

@Pierregadait please check if you are using react and react-dom v17.0.2.

If that works then the support team may get more hints on this problem.

EDIT

After further investigation I guess this is due to the fact that
react 17.0.2 + preact: Build success
react 18.1.0: Build success
react 18.1.0 + preact: WebpackError: TypeError: renderToPipeableStream is not a function

I guess this has nothing to do with the DatoCMS.

hey @Pierregadait I'm sorry but we are in touch with Gatsby to understand where the problem is. Unfortunately it's between us and Gatsby Cloud, so it's out of our complete control and we don't really have much clue of what's going wrong :(

We already have booked some time with Gatsby to better understand where the problem is, I hope to get you some news soon, sorry :(

@Pierregadait since the build works locally it might work also in other build tools, like Netlify or Vercel maybe. So instead of building in Gatsby Cloud you can use that for preview purposes and something else for building? I think it should work fine already.

hey @Pierregadait please try running

yarn upgrade gatsby-source-datocms which should in turn upgrade our JS client which has a change that should fix your issue.

Please let me know if that solves your problem!

I'm going to close the issue as it's just adding confusion.

We have issued a fix for the last problem that was reported, we are going to carry on the discussion over support.