search

DS4PS / cpp-527-fall-2020

http://ds4ps.org/cpp-527-fall-2020/
0 stars 1 forks source link

GitHub Pages failed to build your site #33

Open nicolehillsmall opened 3 years ago

nicolehillsmall commented 3 years ago

When trying to commit new changes, I keep getting the following error:

You have an error on line 18 of your _config.yml file.

I don't see anything out of the ordinary with line 18 though...

Screen Shot 2020-09-23 at 6 28 06 PM

@lecy

lecy commented 3 years ago

I don't see anything obvious, but it is helpful to include the actual code instead of a screen shot for inspection.

Note that things like using tabs instead of spaces, absences of spaces after colons, and other small things can break the YAML headers (I can't check these from the image you sent).

This page is helpful and suggests a validator that you can try:

https://help.github.jp/enterprise/2.11/user/articles/page-build-failed-config-file-error/

nicolehillsmall commented 3 years ago

UPDATE:

I had a teeny tiny extra space before Table

Screen Shot 2020-09-24 at 2 28 04 PM

lecy commented 3 years ago

Got it!

It places the error at the start of the table (line 18) even though it was at 23.

Did you find this with the YAML de-linter?

nicolehillsmall commented 3 years ago

I did use the YAML delinter and it gave me this error for that code chunk :

Error : You cannot define a mapping item when in a sequence Line : undefined undefined

lecy commented 3 years ago

OK, I was curious how well it would work.

Sounds like it was not perfect!

But it at least confirmed there was an anomaly.

Now you can see why I like that R completely ignores spaces :-)

krbrick commented 3 years ago

I had this same error. I reformatted all of the resources because I couldn't find what was tripping me up. Worked out tho!

lecy commented 3 years ago

YAML stresses me out. It is very sensitive to spaces and things like quotes around values.

I take extra caution when editing YAML fields to make sure extra spaces don't find their way into the code and everything has consistent styling.

Some of the data formats that are older than CSV would use positions in the file to designate columns instead of a delimiter. These had similar issues.

CSV is a second-gen storage format. The new formats like JSON use brackets around content so there is no ambiguity.

But YAML essentially reverts back to first-generation standards that were abandoned everywhere else. Super simple to create, but also simple to break.

¯\_(ツ)_/¯