Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gatsby develop (yoga-layout) crashes in Gatsby 2.22.0 #24411

Closed
ehannes opened this issue May 24, 2020 · 3 comments
Closed

Gatsby develop (yoga-layout) crashes in Gatsby 2.22.0 #24411

ehannes opened this issue May 24, 2020 · 3 comments
Labels
type: bug An issue or pull request relating to a bug in Gatsby

Comments

@ehannes
Copy link

ehannes commented May 24, 2020

Description

I upgraded gatsby and now I can't run gatsby develop

Steps to reproduce

  1. Create a new Gatsby site with gatsby new ...
  2. Install the following node packages:
    "gatsby": "2.22.0",
    "react": "16.13.1",
    "react-dom": "16.13.1"
  1. Run gatsby develop

Here is a demo project: https://github.com/ehannes/broken-gatsby-develop-command.

Expected result

I would expect the command to run without a crash 😄

Actual result

It crashed with the following error:

$ gatsby develop
/home/foo/broken-gatsby-develop-command/node_modules/yoga-layout-prebuilt/yoga-layout/build/Release/nbind.js:53
        throw ex;
        ^

Error: write EACCES
    at process.target._send (internal/child_process.js:762:20)
    at process.target.send (internal/child_process.js:634:19)
    at action (/home//foo/broken-gatsby-develop-command/node_modules/gatsby-cli/lib/reporter/loggers/ipc/index.js:58:13)
    at dispatch (/home//foo/broken-gatsby-develop-command/node_modules/gatsby-cli/lib/reporter/redux/index.js:54:5)
    at dispatch (/home//foo/broken-gatsby-develop-command/node_modules/gatsby-cli/lib/reporter/redux/internal-actions.js:42:7)
    at dispatch (/home//foo/broken-gatsby-develop-command/node_modules/gatsby-cli/lib/reporter/redux/index.js:33:5)
    at action.forEach.item (/home//foo/broken-gatsby-develop-command/node_modules/gatsby-cli/lib/reporter/redux/index.js:30:28)
    at Array.forEach (<anonymous>)
    at dispatch (/home//foo/broken-gatsby-develop-command/node_modules/gatsby-cli/lib/reporter/redux/index.js:30:12)
    at Reporter.pendingActivity (/home//foo/broken-gatsby-develop-command/node_modules/redux/lib/redux.js:483:12)
    at module.exports (/home//foo/broken-gatsby-develop-command/node_modules/gatsby/dist/commands/develop-process.js:413:21)
    at Object.<anonymous> (/home//foo/broken-gatsby-develop-command/.cache/tmp-6512-KBLW7D8Kj2CY:4:5)
    at Module._compile (internal/modules/cjs/loader.js:778:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
    at Module.load (internal/modules/cjs/loader.js:653:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)

Environment

$ gatsby info --clipboard

  System:
    OS: Linux 5.3 Pop!_OS 18.04 LTS
    CPU: (12) x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
    Shell: 4.4.20 - /bin/bash
  Languages:
    Python: 2.7.17 - /usr/bin/python
  Browsers:
    Chrome: 81.0.4044.129
    Firefox: 75.0
  npmPackages:
    gatsby: 2.22.0 => 2.22.0

Temporary fix

For me, it works to downgrade to gatsby 2.21.40.

@ehannes ehannes added the type: bug An issue or pull request relating to a bug in Gatsby label May 24, 2020
@gatsbot gatsbot bot added the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label May 24, 2020
@LekoArts LekoArts removed the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label May 25, 2020
@LekoArts
Copy link
Contributor

Thank you for opening this!

This sounds like a duplicate of #22558, #23214 and most specifically #22991 (comment)

gatsby@2.20.0 is not the latest version of Gatsby and as the last comment suggests a bug existed in the CLI, too. So I used gatsby new with the latest version of the gatsby-cli package and followed your steps, I don't see the error with the latest versions of everything. I'd suggest updating your packages :)

We're marking this issue as answered and closing it for now but please feel free to comment here if you would like to continue this discussion. We also recommend heading over to our communities if you have questions that are not bug reports or feature requests. We hope we managed to help and thank you for using Gatsby!

@ehannes
Copy link
Author

ehannes commented May 27, 2020

Hi @LekoArts! Thanks for your response. Unfortunately, it still doesn't work for me, even after upgrading gatsby, gatsby-cli and node. But I will move to one of the other issues. Sorry for not checking that more thoroughly before opening a new one!

@ehannes
Copy link
Author

ehannes commented Sep 18, 2020

This seems to be resolved now :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug An issue or pull request relating to a bug in Gatsby
Projects
None yet
Development

No branches or pull requests

2 participants