Congratulations on creating the one billionth repository on GitHub
51–60 of 146 posts
Re: Congratulations on creating the one billionth repository on GitHub
#52Earlier quoted context omitted.
It's pretty easy to game this. Just keep creating repos till you hit # one billion and remove the old ones. Their API makes it trivial. The only issue will be rate limits, and other people simultaneously creating repos, so it's a matter of luck.
There was a guy who got fired from Meta for creating excessive automated diffs in pursuit of a certain magic number
Re: Congratulations on creating the one billionth repository on GitHub
#53Awesome! 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
The company where I did my stint as CTO I turned up, noticed they were using 32-bit integers as primary keys on one of their key tables that already had 1.3 billion rows and, at the rate they were adding them, would overflow on primary key values within months… so we ran a fairly urgent project to upgrade the IDs to 64-bit to avoid the total meltdown that would have ensued otherwise.
Re: Congratulations on creating the one billionth repository on GitHub
#54This is either staged, or incredible commentary on most github repos , having no purpose, never being realized, and even having given up dreaming .
Re: Congratulations on creating the one billionth repository on GitHub
#55This is either staged, or incredible commentary on most github repos , having no purpose, never being realized, and even having given up dreaming .
Re: Congratulations on creating the one billionth repository on GitHub
#56Earlier quoted context omitted.
The company where I did my stint as CTO I turned up, noticed they were using 32-bit integers as primary keys on one of their key tables that already had 1.3 billion rows and, at the rate they were adding them, would overflow on primary key values within months… so we ran a fairly urgent project to upgrade the IDs to 64-bit to avoid the total meltdown that would have ensued otherwise.
heh, that's happened at at least 5 companies I have worked at - go to check the database, find - currency as floats, hilarious indexes, integers gonna overflow, gigantic types with nothing in them.
Re: Congratulations on creating the one billionth repository on GitHub
#57Earlier quoted context omitted.
Tres commas
Commits that go like \o/ this.
Re: Congratulations on creating the one billionth repository on GitHub
#58Re: Congratulations on creating the one billionth repository on GitHub
#59> https://ohshitgit.com
Re: Congratulations on creating the one billionth repository on GitHub
#60This is either staged, or incredible commentary on most github repos , having no purpose, never being realized, and even having given up dreaming .
I really hope it's the latter, that would be quite brilliant
I mean maybe he made that repo because he'd given up on his coding dreams. Almost.
That would be some interesting accidental meta commentary on the state of things.