Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

Cannot generate the website #75

Closed
chikamichi opened this Issue · 14 comments

3 participants

@chikamichi
Owner

When running bundle exec rake generate, the build fails in-between zh_cn and zh_TW (I guess):

$ bundle exec rake generate
…
rake aborted!
no implicit conversion of nil into String
/home/jd/dev/ruby/www.ruby-lang.org/_plugins/news.rb:13:in `join'
/home/jd/dev/ruby/www.ruby-lang.org/_plugins/news.rb:13:in `initialize'
/home/jd/dev/ruby/www.ruby-lang.org/_plugins/news.rb:102:in `initialize'
/home/jd/dev/ruby/www.ruby-lang.org/_plugins/news.rb:154:in `new'
/home/jd/dev/ruby/www.ruby-lang.org/_plugins/news.rb:154:in `block in generate'
/home/jd/dev/ruby/www.ruby-lang.org/_plugins/news.rb:153:in `each'
/home/jd/dev/ruby/www.ruby-lang.org/_plugins/news.rb:153:in `generate'
/home/jd/dev/ruby/www.ruby-lang.org/vendor/gems/jekyll-0.12.1/lib/jekyll/site.rb:191:in `block in generate'
/home/jd/dev/ruby/www.ruby-lang.org/vendor/gems/jekyll-0.12.1/lib/jekyll/site.rb:189:in `each'
/home/jd/dev/ruby/www.ruby-lang.org/vendor/gems/jekyll-0.12.1/lib/jekyll/site.rb:189:in `generate'
/home/jd/dev/ruby/www.ruby-lang.org/vendor/gems/jekyll-0.12.1/lib/jekyll/site.rb:40:in `process'
/home/jd/dev/ruby/www.ruby-lang.org/Rakefile:347:in `block in <top (required)>'
/home/jd/dev/ruby/www.ruby-lang.org/vendor/gems/rake-10.0.4/lib/rake/task.rb:246:in `call'
/home/jd/dev/ruby/www.ruby-lang.org/vendor/gems/rake-10.0.4/lib/rake/task.rb:246:in `block in execute'
/home/jd/dev/ruby/www.ruby-lang.org/vendor/gems/rake-10.0.4/lib/rake/task.rb:241:in `each'
/home/jd/dev/ruby/www.ruby-lang.org/vendor/gems/rake-10.0.4/lib/rake/task.rb:241:in `execute'
/home/jd/dev/ruby/www.ruby-lang.org/vendor/gems/rake-10.0.4/lib/rake/task.rb:184:in `block in invoke_with_call_chain'
/home/jd/dev/ruby/www.ruby-lang.org/vendor/gems/rake-10.0.4/lib/rake/task.rb:177:in `invoke_with_call_chain'
/home/jd/dev/ruby/www.ruby-lang.org/vendor/gems/rake-10.0.4/lib/rake/task.rb:170:in `invoke'
/home/jd/dev/ruby/www.ruby-lang.org/vendor/gems/rake-10.0.4/lib/rake/application.rb:143:in `invoke_task'
/home/jd/dev/ruby/www.ruby-lang.org/vendor/gems/rake-10.0.4/lib/rake/application.rb:101:in `block (2 levels) in top_level'
/home/jd/dev/ruby/www.ruby-lang.org/vendor/gems/rake-10.0.4/lib/rake/application.rb:101:in `each'
/home/jd/dev/ruby/www.ruby-lang.org/vendor/gems/rake-10.0.4/lib/rake/application.rb:101:in `block in top_level'
/home/jd/dev/ruby/www.ruby-lang.org/vendor/gems/rake-10.0.4/lib/rake/application.rb:110:in `run_with_threads'
/home/jd/dev/ruby/www.ruby-lang.org/vendor/gems/rake-10.0.4/lib/rake/application.rb:95:in `top_level'
/home/jd/dev/ruby/www.ruby-lang.org/vendor/gems/rake-10.0.4/lib/rake/application.rb:73:in `block in run'
/home/jd/dev/ruby/www.ruby-lang.org/vendor/gems/rake-10.0.4/lib/rake/application.rb:160:in `standard_exception_handling'
/home/jd/dev/ruby/www.ruby-lang.org/vendor/gems/rake-10.0.4/lib/rake/application.rb:70:in `run'
Tasks: TOP => generate
(See full trace by running task with --trace)

Does anyone have the issue?

It occurs on a fresh git clone. Gems were installed in vendor/.

@stomar
Owner
I have seen this before, occasionally. Haven't figured out the reason. Trying again up to now always worked...

Update: seemingly unrelated.

@chikamichi
Owner

Hum, it never works for me :/ Any advice?

@stomar
Owner

I use Ruby 1.9.3p392 (rvm).

@chikamichi
Owner

I have a segfault in nokogiri-1.5.9 when switching to 1.9.3-p392 (was using 2.0.0-p0). Which version do you use?

@stomar
Owner

Same. And I just successfully generated with fresh clone and 2.0.0-p0.

@chikamichi
Owner

It seems Jekyll throws some dull posts in. I added a few debug output in _plugins/news.rb in the Index class:

base: /home/jd/dev/ruby/www.ruby-lang.org, LAYOUT: news.html, lang: 
posts:
[<Post: /vendor/gems/jekyll-0.12.1/test/source/2008/02/02/published>, <Post: /vendor/gems/jekyll-0.12.1/test/source/category/2008/09/23/categories>, <Post: /vendor/gems/jekyll-0.12.1/test/source/z_categor$
/2008/09/23/categories>, <Post: /vendor/gems/jekyll-0.12.1/test/source/2008/10/18/foo-bar>, <Post: /vendor/gems/jekyll-0.12.1/test/source/2008/11/21/complex>, <Post: my_category/permalinked-post>, <Post: $
vendor/gems/jekyll-0.12.1/test/source/foo/2008/12/12/topical-post>, <Post: /vendor/gems/jekyll-0.12.1/test/source/2008/12/13/include>, <Post: /vendor/gems/jekyll-0.12.1/test/source/2009/01/27/array-catego$
ies>, <Post: /vendor/gems/jekyll-0.12.1/test/source/2009/01/27/categories>, <Post: /vendor/gems/jekyll-0.12.1/test/source/2009/01/27/category>, <Post: /vendor/gems/jekyll-0.12.1/test/source/2009/01/27/emp$
y-categories>, <Post: /vendor/gems/jekyll-0.12.1/test/source/2009/01/27/empty-category>, <Post: /vendor/gems/jekyll-0.12.1/test/source/2009/03/12/hash-#1>, <Post: /vendor/gems/jekyll-0.12.1/test/source/20$
9/05/18/empty-tag>, <Post: /vendor/gems/jekyll-0.12.1/test/source/2009/05/18/empty-tags>, <Post: /vendor/gems/jekyll-0.12.1/test/source/2009/05/18/tag>, <Post: /vendor/gems/jekyll-0.12.1/test/source/2009/$
5/18/tags>, <Post: /vendor/gems/jekyll-0.12.1/test/source/win/2009/05/24/yaml-linebreak>, <Post: /vendor/gems/jekyll-0.12.1/test/source/2009/06/22/empty-yaml>, <Post: /vendor/gems/jekyll-0.12.1/test/sourc$
/2009/06/22/no-yaml>, <Post: /vendor/gems/jekyll-0.12.1/test/source/2010/01/08/triple-dash>, <Post: /vendor/gems/jekyll-0.12.1/test/source/2010/01/10/date-override>, <Post: /vendor/gems/jekyll-0.12.1/test$
source/2010/01/10/override-data>, <Post: /vendor/gems/jekyll-0.12.1/test/source/2010/01/10/time-override>, <Post: /vendor/gems/jekyll-0.12.1/test/source/2010/01/10/timezone-override>, <Post: /vendor/gems/$
ekyll-0.12.1/test/source/2011/04/12/text-extension>, <Post: /vendor/gems/jekyll-0.12.1/test/source/2011/04/12/md-extension>]

Those are included in site.posts for some reason. Maybe because my gems are vendored?

@chikamichi
Owner

I excluded the vendor directory and it successfully built the website. I then found this to be a well-known "issue"/fix when hosting a Jekyll instance on Heroku with server-side rendering enabled. @a1c66c0 solves this.

@chikamichi chikamichi closed this
@stomar
Owner

Ok, I overlooked in your backtrace that your gem directory resides in the site dir. Jekyll of course doesn't treat that differently from any other subdirectories (_vendor on the other hand would be ignored).

@chikamichi
Owner

Yes, that came obvious once I saw the path in the debug output… but I did not think of it prior to that :)

@chikamichi
Owner

Oh, about the segfault with nokogiri: I removed my vendored gems and reinstalled them all after I switched from 2.0 to 1.9.3 to fix the issue. I did not retry with 2.0 yet, but I will.

@postmodern
Owner

Might want to setup a .bundle/config file so gems are installed into _vendor. Or possibly stop using bundler, since contributors will only use jekyll and maintainers will use mina to deploy.

@stomar
Owner

I would prefer this solution (i.e. _vendor), too, since exclude is rather broken ( all directories and files in the directory tree with the name vendor will be excluded).

@chikamichi
Owner

Oh, really? Jekyll is that eager?

Ok then, I'll remove the gitignore and exclude rules and provide a tailored .bundle config tonight.

@stomar
Owner

Well, it actually shouldn't be that much of an issue since a different file/dir named vendor is not very likely to appear in the directory tree.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.