Live data from Hacker News

GitHub Broken Download URLs

github.com

81–90 of 101 posts

Re: GitHub Broken Download URLs

#81

Earlier quoted context omitted.

Yes, we do. I’ve been at GitHub longer than we’ve had that office, so I tend to work from home anyways.

That's amazing. Had no idea we had a GitHub office here, let alone in the country! If you're working remotely, are you employed by Californian standards/regulations/benefits or by local ones here in Denmark? If you don't mind me asking.

I am employed here in Denmark, wouldn’t have it any other way.

Re: GitHub Broken Download URLs

#82

Hi everyone. I'm an engineer at GitHub and I just posted a response to this issue here: https://github.com/github/feedback/discussions/8149#discussi... .

> A change in the handling of URL schemes was deployed a couple of days ago This was deployed Thanksgiving week? I realize Github isn't a consumer company, so it doesn't face the same pressures as Amazon, but I'm surprised there wasn't a code freeze so people can have a quiet holiday weekend.

Is everyone at GitHub based in America?

Re: GitHub Broken Download URLs

#83
post #82

Earlier quoted context omitted.

> A change in the handling of URL schemes was deployed a couple of days ago This was deployed Thanksgiving week? I realize Github isn't a consumer company, so it doesn't face the same pressures as Amazon, but I'm surprised there wasn't a code freeze so people can have a quiet holiday weekend.

Is everyone at GitHub based in America?

No, they are not. I know at least one Kiwi who worked remotely for Github from New Zealand.

Re: GitHub Broken Download URLs

#84
post #82

Earlier quoted context omitted.

> A change in the handling of URL schemes was deployed a couple of days ago This was deployed Thanksgiving week? I realize Github isn't a consumer company, so it doesn't face the same pressures as Amazon, but I'm surprised there wasn't a code freeze so people can have a quiet holiday weekend.

Is everyone at GitHub based in America?

No. But this appears to now be the most important online shopping week of the year in all of Europe as well. Shops are abnormally sensitive to outages. You'd expect all kinds of service providers to be extremely conservative with code and config pushes this week due to that. Maybe GitHub is far enough removed from the actual consumers that they don't feel the pressure, but it does seem surprising.

Re: GitHub Broken Download URLs

#86
post #72

Earlier quoted context omitted.

Yep. A bug is something that happens (although too many can be judged). But I don't understand how github didn't already know about the regression, from automated testing or error monitoring. I have high expectations for github, because they have met them.

A sibling comment (from an engineer at GH) has given some insight: https://github.com/github/feedback/discussions/8149#discussi... They have error monitoring, but download URLs are one thing that's tricky to monitor for "errors" correctly because if two URLs 404, how do you know from your Grafana dashboard or whatever which are valid and which aren't? Having run a server whose only purpose is to serve static files my…

That makes sense.

This was reported like it affected all download URLs based on a git tag, which also means all download URLs appearing on github "release" pages.

If so, I'd have expected there would have been some testing that would have caught this too. Of course, sure, bugs in tests happen too.

Obviously bugs happen because bugs happen. I stand by being more disturbed that it took two days to notice and revert to restore the regression than I am by the fact that a regression happened. Users noticed right away and tried to report the problem, it took two days after that for Github to comment on it and to revert, which seems problematic, no? Especially if the bug was really affecting as many download URLs as I think it was reported; if it was only affecting a minority of edge case ones, that's more understandable.

It's never possible to eliminate regressions. (It may be possible to reduce the rate of them of course). But whether by testing or by receiving error reports from users, it ought to be possible to notice all major regressions in less than two days.

Re: GitHub Broken Download URLs

#87

Earlier quoted context omitted.

His point is that if everyone had their own server, everyone would have better uptime than they currently get using github. The complexity and load of github is the problem.

The problem is that you’re computing the probability of one service going down, when I actually care about the union of the downtime of all of the services that I need (or, equivalently, the intersection of their uptime). If every Arch package hosted its own source code, then even if each one of them has better uptime than GitHub, at least one of them is probably going to go down every single day (assuming their upti…

I remain unconvinced. If github goes down, it goes down for everyones projects. If everyone ran their own servers, only one or two packages would go down at a time. So instead of 100% its like 0.1%. And since they're simpler, as per OPs comment, they'd stay up longer. So a distributed git, as it was originally intended to be used, is more robust than a single point of failure like github.

Perhaps githubs value is elsewhere.

Re: GitHub Broken Download URLs

#88
post #23

Whether this specific problem is intentional or not, these kinds of problems show the issue with using a single centralized service for distribution of third-party dependencies. But it's just so much more darned convenient than hosting your own Git server! It would be super cool if there was a decentralized alternative to GitHub, that used Git under the hood. Perhaps one would upload their repositories to a node, whi…

Radicle is trying to build something similar to what you described https://radicle.xyz/ Discoverability will probably need more work though

Do you need to buy ethereum to push a commit?

Re: GitHub Broken Download URLs

#90
post #4

Another gripe; unrelated, but since we're piling on... My username ends in a hyphen. Apparently, that's no longer allowed, though my username appears to be grandfathered in. Trying to give feedback about new experimental features lands me on the GitHub communities site, which is treated as a standalone app and thus requires you to log in via GitHub (it doesn't re-use the existing session token). However, Communities…

I've got you bro, try again in a week

For real? :o
Post reply on HN