I have a project that refused to build on Github pages. Very wierd thing is I only added a google anaytics tag on it but it can't build.
Here is the commit that GitHub does not builds
https://github.com/ojiii/tale/commit/466b1133df9fc6a24d80ddafea686cc480b630ef
and here is the commit that GitHub builds
https://github.com/ojiii/tale/commit/4733ac841f24b0f0e915fa171556cf2a7bfae3b7
The only difference between the two is that I added Google Analytics tag on my header.
The weirder thing is that when try to build it on my computer with the previous 2 commit and this commit https://github.com/ojiii/tale/commit/45e718fa3084e2552c409d8b0f1f1c047a253b13 it fails to build. The error message for all the failures are
There was an error parsing `Gemfile`: There are no gemspecs at C:/Users/pikachu/Documents/Workspace/tale. Bundler cannot continue. GitHub builds it before (except for latest commit) and even published it.
To debug locally replace your Gemfile with this:
source "https://rubygems.org"
gem 'github-pages'
Now you will be using the same gems Github uses.
The above error should be preventing your site to build, so fixing that should bring your site alive again.
Related
So, one of my github actions workflow is giving me an error:
"Command "next" not found."
i really don't know why next isn't being found, i've done an ls earlier and it's running the script in the right folder, next.js is listed as a dependency as seen here
i also had a test workflow running, and that worked perfectly
here are the full logs
this error is very odd, since i just copy and pasted this workflow from another project i have, and there everything works fine
the working deploy workflow: web_deploy.yml
the broken deploy workflow: web_deploy_broken.yml
Answer
i was missing a version entry in my package.json, yes, that's it
You are missing install dependencies step like here
- name: Install dependencies
run: yarn install
It's not github action problem - you are just missing a dependency.
next doesn't come with plain yarn
I can't serve a jekyll site locally and I get notified that there is a problem with GitHub pages when I commit to GitHub.
bundle exec jekyll -v 11:28:34
jekyll 3.7.3
ruby --version 11:28:42
ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-darwin17]
When I run:
bundle exec jekyll serve
will fail and spit out hundreds (more like thousnads) of error messages starting with:
bundler: failed to load command: jekyll (/usr/local/bin/jekyll)
SystemStackError: stack level too deep
/usr/local/lib/ruby/gems/2.5.0/gems/kramdown-1.17.0/lib/kramdown/parser/base.rb:106:in `new'
/usr/local/lib/ruby/gems/2.5.0/gems/kramdown-1.17.0/lib/kramdown/parser/base.rb:106:in `add_text'
/usr/local/lib/ruby/gems/2.5.0/gems/kramdown-1.17.0/lib/kramdown/parser/html.rb:171:in `parse_raw_html'
/usr/local/lib/ruby/gems/2.5.0/gems/kramdown-1.17.0/lib/kramdown/parser/kramdown/html.rb:60:in `handle_kramdown_html_tag'
From what I could tell, this can sometimes happen if you use jekyll serve as opposed to bundle exec jekyll serve and if there is a mismatch between your version of jekyll and the one required by github pages, but here I do use bundle exec and so the correct version of jekyll is used.
jekyll itself works if i try to create a new site with jekyll new blah and i can serve that one locally without a problem, but the combo of jekyll and github pages is giving me grief.
I am puzzled and do not know how to proceed.
All this is on Mac OS X 10.13.6.
Not relating to the original cause of the problem here, but i stumbled upon this and had the error stack level too deep. So i guess this might help someone.
I traced my problem to a field that i named as max in some yaml dictionary in the front matter. Maybe you have named a field which has a special meaning in jekyll.
I don't want build master branch. Instead I would like to build a specific tag which the latest stable release as same as my Desktop Chrome.
This is probably the fastest way to fetch Chromium's source code. Suppose 59.0.3071.115 is the version of Chromium, you wish to build. You run this command:
git fetch https://chromium.googlesource.com/chromium/src.git +refs/tags/59.0.3071.115:chromium_59.0.3071.115
If you don't want the history to be fetched (faster fetching of Chromium source code):
git fetch https://chromium.googlesource.com/chromium/src.git +refs/tags/59.0.3071.115:chromium_59.0.3071.115 --depth 1
Now from your Chromium repo, use the following command to show a list of tags available
git tag
You have to checkout that tag by running
git checkout tags/59.0.3071.115
Then run these commands in the order listed below to pull all the third-party dependencies:
gclient sync
gclient sync --with_branch_heads
gclient runhooks
You can find the dev, beta, canary, latest and stable version info of Chromium from this page: https://www.chromium.org/developers/calendar
Now, you should be able to build Chromium. Let me know, if it works
Out of the blue recently, I started receiving notifications that my Jekyll builds were failing on GitHub Pages:
Page build failed. For more information, see https://help.github.com/articles/troubleshooting-github-pages-builds/.
Besides that, there was no info given, and the site built fine on my local machine. I tried everything I could think of: I built the site locally (worked fine on my machine), I deleted the last few files that had been added (no improvement), and I reset the master branch to exactly as it was when I last had a successful build. I figured for sure the last tactic would work, but I kept getting build failures.
I eventually figured out the answer, which I'm going to write in a moment.
It turned out the problem was that GitHub upgraded their version of Jekyll. I had to come to the solution by two steps:
Upgrade the github-pages gem on my own computer:
$ bundle update github-pages
Discover an interesting new error message:
Liquid Exception: undefined method `gsub' for 1000:Fixnum in /_layouts/post.html
After some fiddling around (and using Jekyll's --verbose option to find where the build was choking), I discovered that this gsub error was caused by a post I had, which was titled "1,000". (It was about a sleepless night, where I tried to count my way to sleep, and gave up after 1,000.) Some updated parser was trying to parse this as a number, apparently. To fix it I changed
title: 1,000
to
title: "1,000"
And voilà, GitHub Pages was satisfied.
when you generate a yeoman project, do you commit the node_modules that is generated into your code repository?
It seems like it is necessary for another developer to check out a project and develop from it, but it seems like a lot of files to commit which seem unrelated to a project itself.
You can just run npm install to get the dependencies installed. However there are multiple benefits to committing your dependencies, which you can read about in this blog post:
Checking in front-end dependencies (for Bower, but applies to npm too)