Earlier quoted context omitted.
When your moat is a billion wide, you tend to walk around in your underwear a bit more I guess.
Excellent Diogenes quote reference.
Do you mean a specific quote here? I couldn't find the reference.
Congratulations on creating the one billionth repository on GitHub
121–130 of 146 posts
Re: Congratulations on creating the one billionth repository on GitHub
#122Earlier quoted context omitted.
Is there any reason for GitHub to hide this information though? How could it be used against them? (I understand many companies default to not expose any information unless forced otherwise.)
The rate of creation is like meh, but being able to enumerate all of the repos might be problematic, following new repos and scanning them for leaked credentials could be a negative... but github may have a feed of new repos anyway? Also, having a sequence implies at least a global lock on that sequence during repo creation. Repo creation could otherwise be a scoped lock. OTOH, it's not necessarily handled that way -…
> but github may have a feed of new repos anyway?
Yes: https://docs.github.com/en/rest/repos/repos?apiVersion=2022-... (you can filter to only show repositories created since a given date).
Re: Congratulations on creating the one billionth repository on GitHub
#123Makes me wonder how many repositories exist in general, from all the local Forgejo and Gitlab servers. Heck, include Subversion and Mercurial and git's other friends (and foes!) Did anyone make a search engine for these yet, so we'd be able to get an estimate by searching for the word "a" or so? (This always seemed like the big upside of centralised GitHub to me: people can actually find your code. I've been thinking…
At Software Heritage, we listed 380M public repositories, 280M of which are on Github: https://archive.softwareheritage.org/
Repository search is pretty limited so far: only full-text search on URLs or in a small list of metadata files like package.json.
Re: Congratulations on creating the one billionth repository on GitHub
#124Earlier quoted context omitted.
What are the challenges of such projects? How many people are usually involved? Does it incur downtimes or significant technical challenges for either the infrastructure or the codebase?
Changing the type of the column is no big deal per se, except on a massive table it’s a non-trivial operation, BUT you also have to change the type in everything that touches it, everywhere it’s assigned or copied, everywhere it’s sent over the wire and deserialized where assumptions might be made, any tests, and on, and on. And god help you if you’ve got stuff like int.MaxValue having a special meaning (we didn’t in…
Well done. Unsung heroes keeping it all going, and unsung villains who chose int32 in the first place long gone :-)
Re: Congratulations on creating the one billionth repository on GitHub
#125Earlier quoted context omitted.
What if you wanted to select "top 100 most expensive products" or number of products between $0.01 and $10, $10.01 and $100, $100.01 and $1000? Sure you could do a full table scan on your products table on both queries but an index on price would speed both queries up a lot if you have a lot of products. Of course you have to determine if the index would be used enough to make up for the extra time on index update wh…
Cheap solution, sure, add an index. But you're asking an OLAP question question of an OLTP system. Questions like that are best asked at least of an out-of-production read replica or better an analytics db.
I don't really understand this - what is an out of production read replica? Why wouldn't it just go to a production read replica?
And what is an "analytics db" in this context?
Re: Congratulations on creating the one billionth repository on GitHub
#126While we are doing cool GitHub repo IDs, the first is here: https://api.github.com/repositories/1 https://github.com/mojombo/grit
And the first commit: https://github.com/mojombo/grit/commit/634396b2f541a9f2d58b0...
Re: Congratulations on creating the one billionth repository on GitHub
#127Awesome! Only a little over a billion more to go before GitHub’s very own OpenAPI Spec can start overflowing int32 on repositories too, just like it already does for workflows run IDs! https://github.com/github/rest-api-description/issues/4511
A couple weeks ago there was some Lua community issues because LuaRocks surpassed 65,535 packages.
There was a conflict between this and the LuaRocks implementation under LuaJIT [1] [2], inflicting pain on a narrow set of users as their CI/CD pipelines and personal workflows failed.
It was resolved pretty quick, but interesting!
[1] https://github.com/luarocks/luarocks/issues/1797
[2] https://github.com/openresty/docker-openresty/issues/276
Re: Congratulations on creating the one billionth repository on GitHub
#128Check 'em! Sick dubs :^)
Re: Congratulations on creating the one billionth repository on GitHub
#129Re: Congratulations on creating the one billionth repository on GitHub
#130That's a perfect one billion repo.