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

Regeneration fails without network access #364

Open
3 of 4 tasks
jpouellet opened this issue Dec 11, 2016 · 3 comments
Open
3 of 4 tasks

Regeneration fails without network access #364

jpouellet opened this issue Dec 11, 2016 · 3 comments

Comments

@jpouellet
Copy link

Before submitting an issue, please be sure to

This issue affects

  • The site generated by GitHub Pages
  • Building sites locally

What did you do (e.g., steps to reproduce)

bundle exec jekyll serve without network connectivity.

What did you expect to happen?

The page to regenerate when local changes are made on disk.

What happened instead?

The page initially generates and serves fine, but on regeneration I get:

% bundle exec jekyll serve       
Configuration file: /home/user/qubesos.github.io/_config.yml
Configuration file: /home/user/qubesos.github.io/_config.yml
            Source: /home/user/qubesos.github.io
       Destination: /home/user/qubesos.github.io/_site
 Incremental build: disabled. Enable with --incremental
      Generating... 
                    done in 9.53 seconds.
 Auto-regeneration: enabled for '/home/user/qubesos.github.io'
Configuration file: /home/user/qubesos.github.io/_config.yml
    Server address: http://127.0.0.1:4000/
  Server running... press ctrl-c to stop.
      Regenerating: 1 file(s) changed at 2016-12-11 08:05:11    GitHub Metadata: No GitHub API authentication could be found. Some fields may be missing or have incorrect data.
   GitHub Metadata: Failed to open TCP connection to api.github.com:443 (No route to host - connect(2) for "api.github.com" port 443)
   GitHub Metadata: Failed to open TCP connection to api.github.com:443 (No route to host - connect(2) for "api.github.com" port 443)
   GitHub Metadata: Failed to open TCP connection to api.github.com:443 (No route to host - connect(2) for "api.github.com" port 443)
   GitHub Metadata: Failed to open TCP connection to api.github.com:443 (No route to host - connect(2) for "api.github.com" port 443)
   GitHub Metadata: Failed to open TCP connection to api.github.com:443 (No route to host - connect(2) for "api.github.com" port 443)
...

indefinitely

Additional information

I am trying to do build and serve the page locally without requiring network access.

The above error comes from the jekyll-github-metadata plugin, but the site does not use any {{ site.github.* }} whatsoever, so it would be nice to be able to simply disable that plugin somehow if not required or desired.

@benbalter
Copy link
Contributor

@parkr if this is new, do you think it may be related to URL logic? Shouldn't it fall back?

@jpouellet
Copy link
Author

I realized since reporting this that it does proceed and stop erroring eventually, but it takes a while (20 timeouts or so), which is a lot of waiting.

@parkr
Copy link
Contributor

parkr commented Jan 24, 2017

Working on this over in jekyll/github-metadata#90.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants