nhoizey / jekyll-postfiles

A Jekyll plugin that copies static files from the _posts to the _site folder
http://nhoizey.github.io/jekyll-postfiles/
MIT License
124 stars 16 forks source link

stack level too deep (SystemStackError) #2

Open LazyZhu opened 8 years ago

LazyZhu commented 8 years ago
C:/tools/ruby23/lib/ruby/gems/2.3.0/gems/jekyll-3.2.1/lib/jekyll/cleaner.rb:73:in `parent_dirs': stack level too deep (SystemStackError)
        from C:/tools/ruby23/lib/ruby/gems/2.3.0/gems/jekyll-3.2.1/lib/jekyll/cleaner.rb:77:in `parent_dirs'
        from C:/tools/ruby23/lib/ruby/gems/2.3.0/gems/jekyll-3.2.1/lib/jekyll/cleaner.rb:77:in `parent_dirs'
        from C:/tools/ruby23/lib/ruby/gems/2.3.0/gems/jekyll-3.2.1/lib/jekyll/cleaner.rb:77:in `parent_dirs'
        from C:/tools/ruby23/lib/ruby/gems/2.3.0/gems/jekyll-3.2.1/lib/jekyll/cleaner.rb:77:in `parent_dirs'
        from C:/tools/ruby23/lib/ruby/gems/2.3.0/gems/jekyll-3.2.1/lib/jekyll/cleaner.rb:77:in `parent_dirs'
        from C:/tools/ruby23/lib/ruby/gems/2.3.0/gems/jekyll-3.2.1/lib/jekyll/cleaner.rb:77:in `parent_dirs'
        from C:/tools/ruby23/lib/ruby/gems/2.3.0/gems/jekyll-3.2.1/lib/jekyll/cleaner.rb:77:in `parent_dirs'
        from C:/tools/ruby23/lib/ruby/gems/2.3.0/gems/jekyll-3.2.1/lib/jekyll/cleaner.rb:77:in `parent_dirs'
         ... 9350 levels...
        from C:/tools/ruby23/lib/ruby/gems/2.3.0/gems/mercenary-0.3.6/lib/mercenary.rb:19:in `program'
        from C:/tools/ruby23/lib/ruby/gems/2.3.0/gems/jekyll-3.2.1/exe/jekyll:13:in `<top (required)>'
        from C:/tools/ruby23/bin/jekyll:23:in `load'
        from C:/tools/ruby23/bin/jekyll:23:in `<main>'

There is similar issue: https://github.com/tsmango/jekyll_alias_generator/issues/12

SummerBuger commented 7 years ago

are you fixed this problem? I can not fix this with the similar issue. @LazyZhu

nhoizey commented 7 years ago

I don't know how to fix this.

Did you try with a newer version of Jekyll?

mohkale commented 4 years ago

I don't think this is an issue with this plugin and I don't think it's still active anyways. This issue should be closed.