Earlier quoted context omitted.
Google's internal build system is called Blaze, and (as I understand it) it supports tons of use cases that the Go tool doesn't: * Distributing build jobs across clusters * Targeting any arbitrary platform, architecture combination * Supporting multiple languages and toolchains * Arbitrary build-time script execution (e.g., code generation)
Bazel is the open-source variant of Blaze: https://bazel.build/about/faq#what%E2%80%99s_up_with_the_wor...
Sourcehut will blacklist the Go module mirror
291–300 of 365 posts
Re: Sourcehut will blacklist the Go module mirror
#292The Go team has been making progress toward a complete fix to this problem. Go 1.19 added "go mod download -reuse", which lets it be told about the previous download result including the Git commit refs involved and their hashes. If the relevant parts of the server's advertised ref list is unchanged since the previous download, then the refresh will do nothing more than the ref list, which is very cheap. The proxy.go…
Hi Russ! Thank you for sharing. I am pleased to hear that there is finally some progress towards a solution for this problem. If you or someone working on the issue can reach out via email (sir@cmpwn.com), I would be happy to discuss the issue further. What you described seems like an incomplete solution, and I would like to discuss some additional details with your team, but it is a good start. I'm also happy to pos…
Re: Sourcehut will blacklist the Go module mirror
#293I'll just rehost my git repos on a git host who doesn't mind actually doing their job as a git host by letting git clients clone git repos.
- peak queries are 2500 requests per hour
- some repos are 4gb in size
- let’s round and say 2000 requests at 1gb = 2000 gb/hour = 48000 gb/day
- AWS bandwidth at $0.02 / gb = $960 / day = $28,800 / month
So, one of the richest companies in the world is charging you nearly $30k monthly because they cannot be bothered to be polite. Would you be ok with that situation?
Re: Sourcehut will blacklist the Go module mirror
#294Re: Sourcehut will blacklist the Go module mirror
#295The Go team has been making progress toward a complete fix to this problem. Go 1.19 added "go mod download -reuse", which lets it be told about the previous download result including the Git commit refs involved and their hashes. If the relevant parts of the server's advertised ref list is unchanged since the previous download, then the refresh will do nothing more than the ref list, which is very cheap. The proxy.go…
I realize in the real world most modules are probably hosted by large providers that can absorb the bandwidth, like Github, but it seems incredibly discourteous to not prioritize the hammering of small providers, especially two years on when the response is still "maybe later this year". I think Drew is right in that he shouldn't take a personalized Sourcehut-only exception because this doesn't address the core issue…
Re: Sourcehut will blacklist the Go module mirror
#296Not a good look for Google here.
Re: Sourcehut will blacklist the Go module mirror
#297But the whole thing is frankly a little rude.
Re: Sourcehut will blacklist the Go module mirror
#298Earlier quoted context omitted.
Clearly it was not satisfactory to you, since it was made over 8 months ago, and you didn't take them up on it. I'm objecting here only to the framing you've created that your ouster from the Go issue forum --- which we can see was done with cause --- is what precipitated this situation.
We can behave like adults, ask why it's not satisfactory, and come to a more agreeable mutual solution, or we can blithely offer an incomplete solution, muzzle the other party, and just continue our DDoS.
Re: Sourcehut will blacklist the Go module mirror
#299Earlier quoted context omitted.
We can behave like adults, ask why it's not satisfactory, and come to a more agreeable mutual solution, or we can blithely offer an incomplete solution, muzzle the other party, and just continue our DDoS.
See, here you just did it again: "muzzle the other party", as if it was causally connected to your disagreement about how the module proxy should work, and not to the abuse you inflicted on members of that community.
In the interest of not feeding the trolls, I think I can safely stop engaging with you on this thread. Or maybe on any thread -- you and I never seem to have a productive conversation on this website.
Re: Sourcehut will blacklist the Go module mirror
#300Earlier quoted context omitted.
> Whether he's a great programmer/contributor not isn't really important here. Why not? Why shouldn't we offer more leeway to more valuable contributors?
Why shouldn't better drivers get to ignore speed limits?