Project

General

Profile

Actions
Copy link

tickets #113803

closed

news.o.o. server (bug)

Added by ddemaio over 2 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
High
Assignee:
cboltz
Category:
-
Target version:
-
Start date:
2022-07-19
Due date:
% Done:

0%

Estimated time:

Description

For some reason, the news.o.o. server isn't pickup up the latest article I published https://github.com/openSUSE/news-o-o/blob/84e3ff96b2f85996c6176c764cc76feca5a70494/_posts/2022-07-18-microos-desktop-use-to-help-with-alp-feedback.md.

The previewer picks it up https://news-o-o-preview.netlify.app/, but news.o.o seems to not be able to pick it up.

Sasi and I had something similar happen back at the end of May. https://github.com/openSUSE/news-o-o/commit/1fbdaf96f97d00c9e5faebe9b4ccfe4d04bf1ce3

Actions
Copy link
 #1

Updated by cboltz over 2 years ago

  • Tracker changed from communication to tickets
  • Status changed from New to Resolved

Just checked - the article appeared in the meantime :-) so whatever was broken seems to be accidentally fixed in the meantime.

Actions
Copy link
 #2

Updated by ddemaio over 2 years ago

  • Status changed from Resolved to Feedback
  • Assignee set to cboltz

Not sure, but it looks like the article I published for today is also experiencing the same issue. Guess we will see if it accidentally fixes itself. :-)

Actions
Copy link
 #3

Updated by cboltz over 2 years ago

  • Status changed from Feedback to Resolved

It did fix itsself, and based on your comment here (at 9:03 UTC, article not yet published) and on github (at 10:24 UTC, article published) I'd even say that nothing was broken - the article had date: 2022-07-20 10:00:00+10:00. Looks like jekyll ignores the timezone part and always assumes UTC (or the server timezone, which is UTC in the openSUSE infrastructure).

For completeness, I'll copy&paste my comment on https://github.com/openSUSE/news-o-o/commit/aaed68b93c073824e5efdc2ab4e939e212dde866#commitcomment-78957898 here:

Well, I remember from the manual jekyll run yesterday that the article was intentionally skipped because of date: 2022-07-20 10:00:00+10:00 which (as of yesterday) was a date in the future.

So if you schedule an article to be published on a specific future date, you shouldn't be too surprised if jekyll honors this ;-)

BTW: The +10:00 doesn't look like an european timezone, not sure if that was intentional.

Actions
Copy link

Also available in: Atom PDF