News for hackers. Stuff that matters.
Re:Incident with Actions and Codespaces by fasteddie31003 on Wednesday October 05, 2022 @12:58PM (#33098131)
I'm working on a proactive 3rd party downtime detection tool called AwareOps. Here is some of the recent data from Github's incidents https://app.awareops.com/whatisdown/orgs/437dc8b8-2386-4ef5-... .
Re:Incident with Actions and Codespaces by remram on Wednesday October 05, 2022 @10:25PM (#33103608)
I was waiting for something like this to pop up. With status pages becoming more and more of a marketing front and therefore more and more useless, it makes a lot of sense.
Re:Incident with Actions and Codespaces by lloydatkinson on Wednesday October 05, 2022 @02:04PM (#33099029)
This is very cool! I had the same idea for a while - I currently just run a .NET cli tool I wrote that reads the various cloud RSS feeds and then goes and scrapes the linked page because the RSS feeds deliberately don’t include the severity etc.

Are you looking for any collaborations or anything? Would be interested in helping if you ever are

Re:Incident with Actions and Codespaces by fasteddie31003 on Wednesday October 05, 2022 @02:22PM (#33099281)
I'd love to chat about the idea. [email protected]
Re:Incident with Actions and Codespaces by nathankleyn on Wednesday October 05, 2022 @11:07AM (#33096519)
Actions and Codespaces are listed as having "degraded performance" now too - seeing a lot of action builds disappear into the ether and never get added to the queue to run.
Re:Incident with Actions and Codespaces by derpsteb on Wednesday October 05, 2022 @11:11AM (#33096571)
5mins later: WAIT, YOU FORGOT ALL THESE 20 RUNS!!!!
Re:Incident with Actions and Codespaces by codechecker4 on Wednesday October 05, 2022 @12:05PM (#33097305)
Yeah 20 or so runs. And I'm like: well they did say added to the queue successfully.
Re:Incident with Actions and Codespaces by javierluraschi on Wednesday October 05, 2022 @12:50PM (#33098006)
10min troubleshoot time * 10K devs troubleshooting GitHub Actions right now... there goes one year for comunal dev productivity.
Re:Incident with Actions and Codespaces by reidjs on Wednesday October 05, 2022 @01:53PM (#33098908)
Balance that against the time saved by having GH actions instead of managing your own Jenkins server or something and it’s pretty fair
Re:Incident with Actions and Codespaces by sophacles on Wednesday October 05, 2022 @05:55PM (#33101683)
And yet, I doubt those 10K devs could collectively produces something in that 10 mins that would come even close to me and a random other person putting in 6 months.

This probably holds if the random person is actively working against whatever the collective goal is.

Re:Incident with Actions and Codespaces by lovehashbrowns on Wednesday October 05, 2022 @01:47PM (#33098823)
I spent a good 20 minutes trying to figure out why actions weren’t running for my PR. Almost lost my marbles until I saw another PR in a different repo also not running actions and I decided to check the GitHub status page. It feels like there should be some sorta warning or alert on GitHub.com when there’s an outage of a component of the site.
Re:Incident with Actions and Codespaces by prettychill on Wednesday October 05, 2022 @03:48PM (#33100441)
It would be great if on the checks tab (or on PRs waiting for checks) they put some notification about downtown / issues. Can't imagine how much time was wasted trying to debug this from end users.
Re:Incident with Actions and Codespaces by lloydatkinson on Wednesday October 05, 2022 @02:06PM (#33099050)
I was using codespaces regularly for working on my site when I’m travelling but it just stopped being able to serve http content one day. I use gitpod mostly now and the speed difference is very noticeable.