Posts on a leap day do not publish #4607
Comments
I can confirm also seeing this issue on a GitHub pages hosted blog (which according to https://pages.github.com/versions/ is Jekyll 3.0.3) (edit: removed links to reproduction due to moving targets) |
Further: If I explicitly add Since (Though since this is a leap year bug, this won't be a problem in <24 hours time. Whee time-dependant bugs!) |
It is not Feb 29 yet. By default, Jekyll does not publish future dated posts. |
That depends on where in the world you're living. I'm in UTC+11, so it's been Feb 29 for ~14.5 hours now.
Trying not to jump in for @dylankb here, but it sounds like this is a cascading issue. I don't know what timezone the GitHub pages servers are in, but since future-posts is now disabled, anyone east of the servers trying to post at certain times of day where their relative date doesn't match the server's date may experience this same issue. The fact this feature comes with Jekyll 3, which has only just been released on GitHub pages (which I assume @dylankb is also using) might be compounding matters. Also, the fact this was logged on a specific-day of the year known for these kind of errors might have created a bias in the error attribution. (In my particular case, I tried to post for Feb 29 on Feb 29, so relative to me, this looked leap-year-related.) |
Take note that many servers follow the best practice of running in UTC, so this may affect many, regardless of where they physically are located. This is particularly true for cloud environments. |
I'm in UTC +800, so for me it is not February 29th yet. I was not aware that Jekyll 3 does not publish future dated posts, so @glasnt is right about the bias towards thinking there was a leap year error going on.
The same thing happened with me; post failed to build with |
Same problem with |
Same like a leap year problem. No file is created in the _site directory. |
For me it does work using Edit: Had the problem with a post dated '2016-02-29 22:21:00' (10:21pm) running the |
Hey everyone! This is a problem with the way the date is parsed, I believe. If you can, please specify a date with the timezone in the post in question. GitHub Pages's servers run in Pacific time and honor Daylight Savings Time. The fix is to add Thanks, all! |
@parkr i'm not hosting on github. |
@dylankb I have just rebuilt my GitHub blog and couldn't see any posts, yes Jekyll 3 definitely does not show future-dated posts! |
@parkr - was the root cause of this issue ever resolved? If so, please let me know by which version, pr, or commit. Thanks. |
@mj1856 I don't think so, I just changed my date system to 2016-02-29 and added a jekyll post with this date and nothing is published, if I switch back to current date, it's OK. |
What version of Jekyll are you using (
jekyll -v
)?I'm using Jekyll 3.1.2
What operating system are you using?
Mac OS Yosemite
What did you do?
(Please include the content causing the issue, any relevant configuration settings, and the command you ran)
I wrote a blog post with in a file
2016-2-29-a-beginners-guide-to-jekyll.md
and put this in my_posts
directory. When runningjekyll serve
this file would not be served up and placed in the_site
directory.What did you expect to see?
I expected to see my post served up as
2016-2-29-a-beginners-guide-to-jekyll.html
in my_site
directory when I ranjekyll serve
.What did you see instead?
Nothing would happen. However, once I changed the date portion of the file to 2016-2-28 the content was served up correctly in the
_site
directory.The text was updated successfully, but these errors were encountered: