[ 
https://issues.apache.org/jira/browse/CALCITE-5106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francis Chuang resolved CALCITE-5106.
-------------------------------------
    Resolution: Fixed

> Upgrade to Jekyll 4 and remove unnecessary dependencies from gemfile for site
> -----------------------------------------------------------------------------
>
>                 Key: CALCITE-5106
>                 URL: https://issues.apache.org/jira/browse/CALCITE-5106
>             Project: Calcite
>          Issue Type: Improvement
>          Components: avatica, site
>            Reporter: Francis Chuang
>            Assignee: Francis Chuang
>            Priority: Major
>             Fix For: avatica-1.21.0, 1.31.0
>
>
> While trying to build and preview the website locally for calcite and 
> calcite-avatica, I noticed that the development mode feature for docker 
> stopped working:
> {{ Auto-regeneration: enabled for '/srv/jekyll'
> /usr/gem/gems/jekyll-3.9.2/lib/jekyll/commands/serve/servlet.rb:3:in 
> `require': cannot load such file -- webrick (LoadError)
>         from 
> /usr/gem/gems/jekyll-3.9.2/lib/jekyll/commands/serve/servlet.rb:3:in `<top 
> (required)>'
>         from /usr/gem/gems/jekyll-3.9.2/lib/jekyll/commands/serve.rb:184:in 
> `require_relative'
>         from /usr/gem/gems/jekyll-3.9.2/lib/jekyll/commands/serve.rb:184:in 
> `setup'
>         from /usr/gem/gems/jekyll-3.9.2/lib/jekyll/commands/serve.rb:102:in 
> `process'
>         from /usr/gem/gems/jekyll-3.9.2/lib/jekyll/commands/serve.rb:93:in 
> `block in start'
>         from /usr/gem/gems/jekyll-3.9.2/lib/jekyll/commands/serve.rb:93:in 
> `each'
>         from /usr/gem/gems/jekyll-3.9.2/lib/jekyll/commands/serve.rb:93:in 
> `start'
>         from /usr/gem/gems/jekyll-3.9.2/lib/jekyll/commands/serve.rb:75:in 
> `block (2 levels) in init_with_program'
>         from /usr/gem/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in 
> `block in execute'
>         from /usr/gem/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in 
> `each'
>         from /usr/gem/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in 
> `execute'
>         from /usr/gem/gems/mercenary-0.3.6/lib/mercenary/program.rb:42:in `go'
>         from /usr/gem/gems/mercenary-0.3.6/lib/mercenary.rb:19:in `program'
>         from /usr/gem/gems/jekyll-3.9.2/exe/jekyll:15:in `<top (required)>'
>         from /usr/local/bundle/bin/jekyll:27:in `load'
>         from /usr/local/bundle/bin/jekyll:27:in `<main>'}}
> This seems to be fixed in Jekyll 4.2.2 and 3.9.2, but the docker image we are 
> using is only updating the 4.x versions: 
> https://github.com/jekyll/jekyll/issues/8523
> However, while trying to update Jekyll, I found it strange that Jekyll was 
> pinned to 3.9.2 and could not be upgraded. Upon further investigation, it 
> looks like github-pages gems locks us to Jekyll 3.9.2 and due to 
> compatibility reasons for Github, they don't seem motivated to upgrade: 
> https://github.com/github/pages-gem/issues/651
> The github-pages gem creates an environment that mirrors the Github pages 
> build environment. However, in our builds happen in a jekyll container in 
> docker using Github actions, so it seems that github-page is not required.
> This issue tracks upgrading to jekyll 4 and removing the github-pages gem for 
> the calcite website.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Reply via email to