What's strange to me is how many hours we've been given the same message. Today is an important day for my organization and not getting any information that hints how long this will last is a huge problem for our planning.
Status.github.com: “We're failing over a data storage system”
51–60 of 173 posts
Re: Status.github.com: “We're failing over a data storage system”
#52Wonder if GitHub is "too useful to fail" at this point. As in, most people and companies won't switch git repo providers unless GitHub is down for many days at a time during the work week.
Re: Status.github.com: “We're failing over a data storage system”
#53What particular services are down? I noticed I can hit the UI.
Re: Status.github.com: “We're failing over a data storage system”
#54What's strange to me is how many hours we've been given the same message. Today is an important day for my organization and not getting any information that hints how long this will last is a huge problem for our planning.
Are you a paying customer of GitHub Enterprise? If not, then you're getting your money's worth.
Snark aside, this is a great time to reassess your deployment strategies and look into things like local apt and pypi proxies. I'm confident you can find similar projects that will transparently cache your dependencies.
Re: Status.github.com: “We're failing over a data storage system”
#55I don't know if they keep changing the text updates with a slightly different version to - prove it's a human that typed it - there is code the prevents repeating twice the same message either way it's entertaining... But it's Monday morning in Australia and we need to release! (yep we do this via pr/tagging etc.)
It is to ensure that the updates get mirrored onto twitter, where exact duplicates can't be posted.
They can't alternate?
Re: Status.github.com: “We're failing over a data storage system”
#56What's strange to me is how many hours we've been given the same message. Today is an important day for my organization and not getting any information that hints how long this will last is a huge problem for our planning.
Are you a paying customer of GitHub Enterprise? If not, then you're getting your money's worth. Snark aside, this is a great time to reassess your deployment strategies and look into things like local apt and pypi proxies. I'm confident you can find similar projects that will transparently cache your dependencies.
I don't know how much my org is paying but it's no small amount, Enterprise no. Are we getting what we pay for? I don't think so, I think effective SLA of 99% isn't good enough for any SasS. But of course you understand that moving away from github is no small decision.
Absolutely is this a perfect time to assess deployment strategies and challenge all the advice of how big a company has to be before it's worth to do X.
Re: Status.github.com: “We're failing over a data storage system”
#57Anyone know if this could be related to the Youtube outage? It's been a while since I've seen these big websites go down.
Github is not hosted by Google and was acquired by Microsoft some time back, so that seems... unlikely.
Re: Status.github.com: “We're failing over a data storage system”
#58I can't add comments to pull requests("you can't do that right now") and any commits pushed to branches are not updating updating the visible status in the web interface, no are newly created branches showing up. However, if you navigate to a new commit directly with its SHA (so you can share it with someone if you really want), it'll show up (so they're just not being indexed). EDIT: Obligatory "that's what happens…
I’m receiving emails (a lot of duplicates) from comments in PR, but they won’t show up in the browser. I guess people are trying to submit multiple times, the email is sent but comment isn’t posted.
Re: Status.github.com: “We're failing over a data storage system”
#59Is that a job of the Microsoft special project team ?
Re: Status.github.com: “We're failing over a data storage system”
#60I don't know if they keep changing the text updates with a slightly different version to - prove it's a human that typed it - there is code the prevents repeating twice the same message either way it's entertaining... But it's Monday morning in Australia and we need to release! (yep we do this via pr/tagging etc.)
I like how the times are unevenly spaced too haha. I'm imagining a bunch of devs sitting at home in their pajamas (Sunday night) talking on Slack as they try to fix the site and every time there's a lull one person's like "hey we should probably refresh the status again".