You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 18, 2021. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 18, 2021. It is now read-only.
😞 Why always mess with the system in the first place? (Rhetorical question, needs no answer.)
Delete the repos, see what happens. Maybe do some real work (this sounds more offensive than it's meant, but still).
I think it's safe to assume that you're the only one affected and you consciously provoked it. The rest of us (and GitHub BTW) is probably safe for the next decades...
I apologize in advance, but...
"I have a (fake) 1000-year streak on GitHub, hihi." Yay! You go, boy! Edit: 🎉 🎈 👏
Don't misinterpret my comment as me not liking you personally or whatnot, you're probably a nice guy when you're not faking commits. 😉
This indicates that the user has pushed commits using a timestamp in 2030, which is causing the issue with calculating and displaying contributions correctly. Currently we don't support this kind of commit activity in the contributions graph.
Assuming they calculate the streak by walking backwards from the current date, I'd say they could probably fix this by bailing out once it reaches February 29, 2008 (the date CrunchBase lists as the founding of GitHub).
And it definitely should be fixed. Isn't something that triggers 502 errors a vector for Denial-of-Service attacks (as it indicates that the server has crashed)?
@stuartpb you're a genious! I think that in the past this might haven been usable to DoS other people because commits are only considered by email and are perfectly falsifieable!
@github: sorry, I hadn't noticed that this had DoS potential against others
Right now, GitHub seems to have pushed a hotfix for that already? https://github.com/cirosantilli-puppet is maxing out at 1000 days: https://github.com/cirosantilli-puppet on a streak from 1990 to 2020 Not sure why 1000, maybe a random maximum number? Also note that there are two empty days before the green days: hovering on them does not say no activity like the others.
But this introduced the bug that commits in the future appear as "authored just now": GitHub shouldn't modify commit data like that, it's confusing:
The real solution is to consider the timestamp of when the commit was pushed for the streak, cache things properly as they are pushed / process things asynchronously and show whatever data is in the repo on the commits.
@stuartpb you're a genious! I think that in the past this might haven been usable to DoS other people because commits are only considered by email and are perfectly falsifieable!
That's true, but I was thinking in terms of DDoSing all of GitHub by making every server spin and crash doing this instead of handling requests.
That's a crazy idea, though: destroy the contribution graph for any user by pushing a fake repository with fake commits. (Maybe GitHub should start only counting signed commits as contributions, for repos the user isn't marked as a contributor to?)
Activity
[-]502 on long streak[/-][+]502 on homepage on long streak[/+]bwin commentedon Mar 21, 2015
😞 Why always mess with the system in the first place? (Rhetorical question, needs no answer.)
Delete the repos, see what happens. Maybe do some real work (this sounds more offensive than it's meant, but still).
I think it's safe to assume that you're the only one affected and you consciously provoked it. The rest of us (and GitHub BTW) is probably safe for the next decades...
I apologize in advance, but...
"I have a (fake) 1000-year streak on GitHub, hihi." Yay! You go, boy! Edit: 🎉 🎈 👏
Don't misinterpret my comment as me not liking you personally or whatnot, you're probably a nice guy when you're not faking commits. 😉
bwin commentedon Mar 21, 2015
BTW since I don't know if you knew:
Edit:
cirosantilli commentedon Mar 21, 2015
@bwin my goals are:
They are all purely for the lolz, non important, and will likely not be furthered by my actions 😉
Yup, I always do: #182
But I bet at least one GitHubber reads this repo.
bwin commentedon Mar 21, 2015
😉
NARKOZ commentedon Mar 23, 2015
That's a unique way to hide your identity by slaying unicorns.
And according to Github, it isn't a bug, but feature:
Deal with it!
cirosantilli commentedon Mar 23, 2015
@NARKOZ GitHub's definition of "bug" is quite strict if they don't consider 502 as bugs 😄
I could also make it 1000 years in the past if they like 😉
Can you point to where did you got the quote from just for reference? Or was it a support request that you've made?
NARKOZ commentedon Mar 23, 2015
@cirosantilli excerpt from a support ticket.
stuartpb commentedon Mar 25, 2015
Assuming they calculate the streak by walking backwards from the current date, I'd say they could probably fix this by bailing out once it reaches February 29, 2008 (the date CrunchBase lists as the founding of GitHub).
stuartpb commentedon Mar 25, 2015
And it definitely should be fixed. Isn't something that triggers 502 errors a vector for Denial-of-Service attacks (as it indicates that the server has crashed)?
cirosantilli commentedon Mar 25, 2015
@stuartpb you're a genious! I think that in the past this might haven been usable to DoS other people because commits are only considered by email and are perfectly falsifieable!
@github: sorry, I hadn't noticed that this had DoS potential against others
Right now, GitHub seems to have pushed a hotfix for that already? https://github.com/cirosantilli-puppet is maxing out at 1000 days: https://github.com/cirosantilli-puppet on a streak from 1990 to 2020 Not sure why 1000, maybe a random maximum number? Also note that there are two empty days before the green days: hovering on them does not say no activity like the others.
But this introduced the bug that commits in the future appear as "authored just now": GitHub shouldn't modify commit data like that, it's confusing:
The real solution is to consider the timestamp of when the commit was pushed for the streak, cache things properly as they are pushed / process things asynchronously and show whatever data is in the repo on the commits.
stuartpb commentedon Mar 25, 2015
That's true, but I was thinking in terms of DDoSing all of GitHub by making every server spin and crash doing this instead of handling requests.
That's a crazy idea, though: destroy the contribution graph for any user by pushing a fake repository with fake commits. (Maybe GitHub should start only counting signed commits as contributions, for repos the user isn't marked as a contributor to?)
stuartpb commentedon Mar 25, 2015
Indeed, it would appear GitHub already doesn't track contributions on repos you don't own: I just pushed 10000+ commits by cirosantilli-puppet to https://github.com/stuartpb/test-streak and they haven't moved the needle on https://github.com/cirosantilli-puppet.
NARKOZ commentedon Mar 25, 2015
The same reason why @GoogleCodeExporter's contributions don't count.
cirosantilli commentedon May 20, 2016
Streak is dead. Long live streak: https://github.com/blog/2173-more-contributions-on-your-profile