Warning: Event "xstate.after(1000)#waitingMachine.batchingNodeMutations" / Error Socket Hangups / Hot Reload Issues (no changes taking effect)

[tr1s]

Description

Hot reloading is not working at all.

Steps to reproduce

running gatsby develop or netlify dev, making a change, then getting this message immediately on change:

warning Warning: Event "xstate.after(1000)#waitingMachine.batchingNodeMutations" was sent to stopped service "waitingMachine". This service has already reached its final state, and will not transition.
Event: {"type":"xstate.after(1000)#waitingMachine.batchingNodeMutations"}

I saw this message pop up yesterday a few times, but changes were still applying. Now no updates will take effect and I'm stuck with this message popping up.

I've also had it tell me "error socket hangup" in-between them:

and I've also noticed about an hour ago that when it was updating, it would take 10+ seconds to work, then update every single page...

Any help would be greatly appreciated right now as this is a live production site I'm trying to work on.

Thanks!

Environment

  System:
    OS: macOS 10.15.6
    CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 14.4.0 - ~/.nvm/versions/node/v14.4.0/bin/node
    Yarn: 1.22.4 - /usr/local/bin/yarn
    npm: 6.14.7 - ~/.nvm/versions/node/v14.4.0/bin/npm
  Languages:
    Python: 2.7.16 - /usr/bin/python
  Browsers:
    Chrome: 84.0.4147.125
    Safari: 13.1.2
  npmPackages:
    gatsby: ^2.24.15 => 2.24.15
    gatsby-image: ^2.4.14 => 2.4.14
    gatsby-plugin-catch-links: ^2.3.11 => 2.3.11
    gatsby-plugin-hotjar: ^1.0.1 => 1.0.1
    gatsby-plugin-manifest: ^2.4.21 => 2.4.21
    gatsby-plugin-netlify: ^2.3.11 => 2.3.11
    gatsby-plugin-offline: ^3.2.21 => 3.2.21
    gatsby-plugin-react-helmet-async: ^1.0.17-0 => 1.0.17-0
    gatsby-plugin-robots-txt: ^1.5.1 => 1.5.1
    gatsby-plugin-sass: ^2.3.12 => 2.3.12
    gatsby-plugin-segment-js: ^3.3.0 => 3.3.0
    gatsby-plugin-sharp: ^2.6.24 => 2.6.24
    gatsby-plugin-sitemap: ^2.4.11 => 2.4.11
    gatsby-remark-images: ^3.3.23 => 3.3.25
    gatsby-remark-relative-images: ^0.2.3 => 0.2.3
    gatsby-source-contentful: ^2.3.34 => 2.3.37
    gatsby-source-filesystem: ^2.3.23 => 2.3.24
    gatsby-transformer-remark: ^2.8.27 => 2.8.28
    gatsby-transformer-sharp: ^2.5.12 => 2.5.13
  npmGlobalPackages:
    gatsby-cli: 2.12.66

[cescoferraro]

I am getting the same error. Also running OSX

[theskillwithin]

recently hot reloading for me has been super buggy, sometimes it only works 1 out of every 5 saves. especially with styled components styles. I can even refresh and it doesn't update, i have to restart build. or try saving 20 times.
also on OSX

but i don't see this warning

edit:
not sure if this is related, but some reason there is a nodejs debugger started on gatsby develop for me?
in vscode with auto attach off, and fresh terminal outside of vscode

➜  schwayweb git:(master) npm start

> schwayweb@0.1.0 start /Users/Austin/Projects/schwayweb
> npm run develop


> schwayweb@0.1.0 develop /Users/Austin/Projects/schwayweb
> gatsby develop

Debugger listening on ws://127.0.0.1:9229/95b949f9-6f5f-45e6-bf06-92f274139cbc
For help, see: https://nodejs.org/en/docs/inspector
success open and validate gatsby-configs - 0.051s
success load plugins - 1.246s
success onPreInit - 0.045s
success initialize cache - 0.007s
success copy gatsby files - 0.079s
success onPreBootstrap - 0.017s

[gchallen]

Seeing the same problem—both the warning message and stalled build. Super frustrating since restarting the build is really slow...

[vladar]

This is a duplicate of #26192 Let's track it there. Also, check out #26192 (comment) maybe it will help (probably an upstream xstate bug)