Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitHub Major Service Outage

news.ycombinator.com

Post reply on HN
Print view View original

11–20 of 85 posts

Re: GitHub Major Service Outage

#11

Post by i336_ »

tyingq wrote: post #8

Seeing an interesting thing where my github issue comments just posted are apparently posted a short time in the future. http://imgur.com/a/eQSc9 Doesn't seem to break anything, but it is a bit curious. May not be new though...I just happened to notice it today.

I've noticed this behavior with a lot of services.

I can only chalk it up to something like clock drift between the processing node and the database server.

Irritatingly I can't remember which site it was but I posted something somewhere a couple days ago and immediately after hitting enter the site marked what I'd said as submitted "a few seconds from now". I never fail to be amused that the fuzzy time library being used has code specifically designed to handle this edge case scenario. :D

Re: GitHub Major Service Outage

#13

Post by i336_ »

As of right now...

On the one hand, I see "Everything operating normally." at the top in green, and no flags or alerts.

On the other hand, the charts look good, but "App server availability" looks interesting, the right edge of the chart is pretty much at 0%.

Re: GitHub Major Service Outage

#14

Post by drinchev »

A bit weird. GitHub says they fixed it, but on the other hand CircleCI still considers it as an outage :

> Monitoring

> May 31, 2017 3:08 PM

> GitHub have declared the outage resolved and we are starting to see incoming GitHub hooks. Builds are being triggered again. However we are still seeing failures with the GitHub API. This continues to prevent our webapp > from fetching data from GitHub. We are monitoring the situation and will ensure sufficient capacity for when their service resumes normal operations.

Re: GitHub Major Service Outage

#15

Post by toomuchtodo »

i336_ wrote: post #11
tyingq wrote: post #8

Seeing an interesting thing where my github issue comments just posted are apparently posted a short time in the future. http://imgur.com/a/eQSc9 Doesn't seem to break anything, but it is a bit curious. May not be new though...I just happened to notice it today.

I've noticed this behavior with a lot of services. I can only chalk it up to something like clock drift between the processing node and the database server. Irritatingly I can't remember which site it was but I posted something somewhere a couple days ago and immediately after hitting enter the site marked what I'd said as submitted "a few seconds from now". I never fail to be amused that the fuzzy time library being…

Message queues and eventual consistency. Unless your request requires something "atomicy", 200/201 response should be a sign of "got the message, will get to work on it when we can".

Re: GitHub Major Service Outage

#16

Post by epicide »

i336_ wrote: post #11
tyingq wrote: post #8

Seeing an interesting thing where my github issue comments just posted are apparently posted a short time in the future. http://imgur.com/a/eQSc9 Doesn't seem to break anything, but it is a bit curious. May not be new though...I just happened to notice it today.

I've noticed this behavior with a lot of services. I can only chalk it up to something like clock drift between the processing node and the database server. Irritatingly I can't remember which site it was but I posted something somewhere a couple days ago and immediately after hitting enter the site marked what I'd said as submitted "a few seconds from now". I never fail to be amused that the fuzzy time library being…

I don't think it's really an edge case. Probably one of the main uses, actually.

Sure, if you use it to show comment age, you shouldn't ever see it, but I'm sure they fully support using it for countdowns, too.

EDIT: it's the 4th example under relative time for Moment.js (https://momentjs.com/).

Re: GitHub Major Service Outage

#17

Post by Piskvorrr »

i336_ wrote: post #11
tyingq wrote: post #8

Seeing an interesting thing where my github issue comments just posted are apparently posted a short time in the future. http://imgur.com/a/eQSc9 Doesn't seem to break anything, but it is a bit curious. May not be new though...I just happened to notice it today.

I've noticed this behavior with a lot of services. I can only chalk it up to something like clock drift between the processing node and the database server. Irritatingly I can't remember which site it was but I posted something somewhere a couple days ago and immediately after hitting enter the site marked what I'd said as submitted "a few seconds from now". I never fail to be amused that the fuzzy time library being…

Actually, most of the "relative time" JS libraries can be used for countdown as well ("this event is scheduled in two hours"). Accidentally getting a timestamp that's supposed to be in the past shouldn't break it :)

Re: GitHub Major Service Outage

#20

Post by i336_ »

Piskvorrr wrote: post #17
i336_ wrote: post #11

Earlier quoted context omitted.

I've noticed this behavior with a lot of services. I can only chalk it up to something like clock drift between the processing node and the database server. Irritatingly I can't remember which site it was but I posted something somewhere a couple days ago and immediately after hitting enter the site marked what I'd said as submitted "a few seconds from now". I never fail to be amused that the fuzzy time library being…

Actually, most of the "relative time" JS libraries can be used for countdown as well ("this event is scheduled in two hours"). Accidentally getting a timestamp that's supposed to be in the past shouldn't break it :)

Very true.

I just think there should be an intent argument specifiable to the library to indicate that the duration in question refers to an event that has happened in the past.

In such a scenario, the library should mark the duration as happening "just now" and possibly flag a warning or raise an exception.

The reason I say this is that, humanly speaking, "Your message was sent 23 seconds from now" is amusing at best to developers who know what's happening (negative time delta) and linguistically confusing to general users ("was sent" vs "from now").

Post reply on HN