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

Jekyll error on jekyll serve -- fsevent: running worker failed #6189

Closed
chadcodes opened this issue Jun 29, 2017 · 10 comments

Comments

Projects
None yet
9 participants
@chadcodes
Copy link

commented Jun 29, 2017

  • I believe this to be a bug, not a question about using Jekyll.
  • I updated to the latest Jekyll (or) if on GitHub Pages to the latest github-pages
  • I ran jekyll doctor to check my configuration

  • I am on (or have tested on) macOS 10+

  • I was trying to build.

My Reproduction Steps

I created a new Jekyll site in my current directory with:
jekyll new .

Then tried to serve the site with:
jekyll serve

The Output I Wanted

I get 2 errors:

Deprecation: The 'gems' configuration option has been renamed to 'plugins'. Please update your config file accordingly.

Easily fixed by changing the _config.yml file.

Second error I'm stuck on:

ERROR -- : fsevent: running worker failed: wrong number of arguments (given 2, expected 1)

@crispgm

This comment has been minimized.

Copy link
Member

commented Jun 29, 2017

I encountered the same error today, which never happened before. I guess it might be wrong with rb-fsevent. Would you mind posting Gemfile.lock?

@DirtyF

This comment has been minimized.

Copy link
Member

commented Jun 29, 2017

@chadcodes The first message is not an error, it's simply a notice asking you to rename the gemslist to plugins in the _config.yml. This change happened in 3.5.0.

Didn't reproduce your issue on MacOS. Could you post bundle envoutput?

@ashmaroli

This comment has been minimized.

Copy link
Member

commented Jun 29, 2017

The first message is not an error

Technically, it is not an error.. but Deprecator does log this message at level :error 😬

@kentaroi

This comment has been minimized.

Copy link

commented Jun 29, 2017

On the second error, a temporary workaround is as follows:

  • Add the following line to your Gemfile
 gem "rb-fsevent", "~> 0.9.0"
  • Run the command bundle update rb-fsevent in your shell
@chadcodes

This comment has been minimized.

Copy link
Author

commented Jun 29, 2017

@kentaroi your solution worked, thank you very much!

@pathawks

This comment has been minimized.

Copy link
Member

commented Jun 29, 2017

What version of rb-fsevent were you running? Is this something that others are likely to encounter?

@kentaroi

This comment has been minimized.

Copy link

commented Jun 29, 2017

Actually, I also encountered this issue, when the version of rb-fsevent was 0.10.1.
There already is a PR guard/listen#432 to listen gem, which jekyll-watch depends on.

@huphtur

This comment has been minimized.

Copy link

commented Jun 29, 2017

Had the same errors today. For those that never worked with a gem file (like me 😕) make sure to also add gem "jekyll" to the gem file followed by bundle install command as that resolved missing kramdown gem.

@menehune23

This comment has been minimized.

Copy link

commented Jun 30, 2017

I encountered this rb-fsevent issue yesterday and discovered it only happens if jekyll serve is running while you save a file (a post for instance). It also happens if you have your repo open is VS Code while serve is running, even when not saving (which is what took me so long to figure out what triggers it). Hopefully that might explain why some people are not seeing it reproduced.

UPDATE:
Took a look at my Gemfile.lock and it had rb-fsevent (0.10.1). Following the suggestion above for 0.9.X seems to have worked around it.

@kentaroi

This comment has been minimized.

Copy link

commented Jul 1, 2017

This issue was fixed in rb-fsevent 0.10.2
thibaudgg/rb-fsevent@d48b3bb

v1ctorf added a commit to v1ctorf/personal-page-jekyll that referenced this issue Mar 9, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.