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
Liquid Exception: Failed to get header. in 2013-06-04-welcome-to-jekyll.markdown #1181
Comments
It's a problem with pygments.rb in this case. What version of Python do you have on your machine? |
I just encountered the same problem today. At first, I had no versions of python, but I've since tried again with both python 3 and 2.7. Neither changed anything. I'm running on archlinux and using rbenv, if that helps. Edit: The problem doesn't appear on my macbook. |
Looks like it's not exclusively a jekyll issue (unfortunately): |
my python version is 3.3.2. I'm using Archlinux too. |
Pygments does not support 3 at this time. I believe they are working on support though. On Jun 5, 2013, at 6:45 PM, collaboratorium notifications@github.com wrote:
|
Yeah, unfortunately they only support 2.7. As this isn't a problem with Jekyll itself, I going to close this. |
Just got the same today with Python 2.6.1 and Jekyll 1.0.3. Looks like it is not restricted to a Python 3 issue. datum:projects$ jekyll new foo
New jekyll site installed in /Users/tschaub/projects/foo.
datum:projects$ cd foo
datum:foo$ jekyll build --trace
Configuration file: /Users/tschaub/projects/foo/_config.yml
Source: /Users/tschaub/projects/foo
Destination: /Users/tschaub/projects/foo/_site
Generating... Liquid Exception: Failed to get header. in 2013-06-25-welcome-to-jekyll.markdown
/Library/Ruby/Gems/1.8/gems/pygments.rb-0.5.0/lib/pygments/popen.rb:357:in `get_header': Failed to get header. (MentosError)
from /Library/Ruby/Gems/1.8/gems/pygments.rb-0.5.0/lib/pygments/popen.rb:235:in `mentos'
from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/timeout.rb:67:in `timeout'
from /Library/Ruby/Gems/1.8/gems/pygments.rb-0.5.0/lib/pygments/popen.rb:209:in `mentos'
from /Library/Ruby/Gems/1.8/gems/pygments.rb-0.5.0/lib/pygments/popen.rb:192:in `highlight'
from /Library/Ruby/Gems/1.8/gems/jekyll-1.0.3/bin/../lib/jekyll/tags/highlight.rb:57:in `render_pygments'
from /Library/Ruby/Gems/1.8/gems/jekyll-1.0.3/bin/../lib/jekyll/tags/highlight.rb:45:in `render'
from /Library/Ruby/Gems/1.8/gems/liquid-2.5.0/lib/liquid/block.rb:106:in `render_all'
from /Library/Ruby/Gems/1.8/gems/liquid-2.5.0/lib/liquid/block.rb:93:in `each'
from /Library/Ruby/Gems/1.8/gems/liquid-2.5.0/lib/liquid/block.rb:93:in `render_all'
from /Library/Ruby/Gems/1.8/gems/liquid-2.5.0/lib/liquid/block.rb:82:in `render'
from /Library/Ruby/Gems/1.8/gems/liquid-2.5.0/lib/liquid/template.rb:124:in `render'
from /Library/Ruby/Gems/1.8/gems/liquid-2.5.0/lib/liquid/template.rb:132:in `render!'
from /Library/Ruby/Gems/1.8/gems/jekyll-1.0.3/bin/../lib/jekyll/convertible.rb:77:in `render_liquid'
from /Library/Ruby/Gems/1.8/gems/jekyll-1.0.3/bin/../lib/jekyll/convertible.rb:125:in `do_layout'
from /Library/Ruby/Gems/1.8/gems/jekyll-1.0.3/bin/../lib/jekyll/post.rb:263:in `render'
from /Library/Ruby/Gems/1.8/gems/jekyll-1.0.3/bin/../lib/jekyll/site.rb:228:in `render'
from /Library/Ruby/Gems/1.8/gems/jekyll-1.0.3/bin/../lib/jekyll/site.rb:227:in `each'
from /Library/Ruby/Gems/1.8/gems/jekyll-1.0.3/bin/../lib/jekyll/site.rb:227:in `render'
from /Library/Ruby/Gems/1.8/gems/jekyll-1.0.3/bin/../lib/jekyll/site.rb:44:in `process'
from /Library/Ruby/Gems/1.8/gems/jekyll-1.0.3/bin/../lib/jekyll/command.rb:18:in `process_site'
from /Library/Ruby/Gems/1.8/gems/jekyll-1.0.3/bin/../lib/jekyll/commands/build.rb:23:in `build'
from /Library/Ruby/Gems/1.8/gems/jekyll-1.0.3/bin/../lib/jekyll/commands/build.rb:7:in `process'
from /Library/Ruby/Gems/1.8/gems/jekyll-1.0.3/bin/jekyll:61
from /Library/Ruby/Gems/1.8/gems/commander-4.1.3/lib/commander/command.rb:180:in `call'
from /Library/Ruby/Gems/1.8/gems/commander-4.1.3/lib/commander/command.rb:180:in `call'
from /Library/Ruby/Gems/1.8/gems/commander-4.1.3/lib/commander/command.rb:155:in `run'
from /Library/Ruby/Gems/1.8/gems/commander-4.1.3/lib/commander/runner.rb:402:in `run_active_command'
from /Library/Ruby/Gems/1.8/gems/commander-4.1.3/lib/commander/runner.rb:78:in `run!'
from /Library/Ruby/Gems/1.8/gems/commander-4.1.3/lib/commander/delegates.rb:7:in `run!'
from /Library/Ruby/Gems/1.8/gems/commander-4.1.3/lib/commander/import.rb:10
from /usr/bin/jekyll:23
datum:foo$ python --version
Python 2.6.1
datum:foo$ jekyll --version
jekyll 1.0.3 |
Try updating to Ruby 1.9 or 2.0 and try again. |
Get this error too =( Ruby 1.8 on Mac OS. |
@Elfet What version of pygments.rb and jekyll? |
@parkr jekyll 1.0.3 and pygments.rb 0.5.1. |
@Elfet What version of python? This is only compatible with 2.6 < x < 3.0 (so not 3 :)) |
Related: pygments/pygments.rb#45 |
Python 2.7.2 (default, Oct 11 2012, 20:14:37) |
Hm, then I'm not sure what the issue is... :/ |
Same with mine. Python 2.7.3 Ruby: 1.9.3-p194. |
Woops. I got the same problem after updating to Lion, installing Xcode and its command line tools. Re-install python 2.7.x fixed it. Thanks. |
Got the same error here on ruby 2.0.0, Python 2.6.1 on OS X 10.6.8. Fixed after install python with homebrew. |
Just for a reference to those who meet the same problem like me. I had python 2.7.6 installed first and then installed python 3.3.0. So re-install python 2.7.6 fixed the problem for me. Thanks @olidin.
|
Same problem
|
@uglyyouth you'll need to use Python 2 in order to get Pygments highlighting with Jekyll. |
Ruby 2.0.0 and Python 3.3.3 has problems. |
Hi, I have also some issues with pygments.rb.
As you can see, I have multiple versions of Ruby and pygments.rb and even tried with Python 2.7.8 and 2.7.6. |
@Macxim Where is your Python installed? |
Actually, I just went to https://www.python.org/downloads/ and selected the 2.7.8 version and followed the installer. |
Which version of posix-spawn do you have installed? |
This one: Edit:
|
because python3 will occurs error with pigments jekyll/jekyll#1181
Still having issues with this on a fresh install, and none of the listed solutions work. |
@mtitolo What is the output of |
@parkr Fresh install on OS X 10.9.4, Python 2.7.8, ruby 2.0.0p481. I did manage to get it working a few hours after my last comment. I've only used python on this machine with virtualenv, but somehow I had to remove a bunch of packages from |
@mtitolo Sorry you ran into that issue. Just so I understand, you |
@parkr correct. I went into the gem, found mentos.py and executed it. The errors were variations on the ones listed in the comment over on the pygments.rb issue, but the path printed was into |
I have never been able to get Pygments to work on Windows so I use Rouge. Today I got this error even though I set
I wonder why it is still trying to use pygments :( |
@qwertie You checked all possible configuration files? |
I am not aware of the existence of any other configuration files. |
@qwertie Check to make sure your |
Yes, there's only one "highlighter". I just realized this could be an old bug since my local PC is still configured for Jekyll 1.5.1, as previously used on GitHub (and since GitHub requires pygments, I always change the highlighter temporarily before uploading _config.yml). It worked 6 months ago, I don't know what changed (oh wait, I did install Python 3.4.1 in the interim). And now I can't update, as "gem install anything" gives an SSL error. Ugh. |
had the same problem on windows 8, using the below resolved the issue pygments.rb latest |
I met the same problem on win7,the issue is: help..... |
I had the same problem. I managed to solve it by using a vitualenv for python with python 2.7 (My default interpreter was 3.4). |
I got the same issue when I was trying to build my Jekyll blog in my ubuntu server. |
I just tried to run
jekyll new website2
and thenjekyll build
and I get the error below.I'm using jekyll version 1.0.2.
(my actual home folder path has been replaced with $HOME)
The text was updated successfully, but these errors were encountered: