-
Notifications
You must be signed in to change notification settings - Fork 29.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A weird commit from 1970 #2713
Comments
Something new for node-accept-pull-request to test for. If the commit is close to HEAD I'd be inclined to support a rebase and fix. |
We briefly discussed this here #2402 (comment) where you also can find the relevant commit. |
@rvagg it was first spotted in #2402 (comment). I am not sure if we can fix it now :( |
@jbergstroem speak of the timing :D |
Too bad when you highlight a span of time in that github timeline, it doesn't zoom that portion to fit the container. |
Here's what's on top of that commit so far:
I personally have no qualms about rebasing a fix on that commit which would obviously mean changing hashes from there onwards, but I'm generally pretty relaxed wrt my git logs. @nodejs/tsc anyone feel strongly about not wanting to mess up the HEAD of the active branches (this would involve v3.x and v4.x too)? |
v8 will silently return an empty handle which doesn't delete our data if string length is above String::kMaxLength Fixes: #1374 PR-URL: #2402 Reviewed-By: trevnorris - Trevor Norris <trev.norris@gmail.com> Reviewed-By: indutny - Fedor Indutny <fedor.indutny@gmail.com> Reviewed-By: bnoordhuis - Ben Noordhuis <info@bnoordhuis.nl>
Uh, +1 fixing the commit. |
v8 will silently return an empty handle which doesn't delete our data if string length is above String::kMaxLength Fixes: #1374 PR-URL: #2402 Reviewed-By: trevnorris - Trevor Norris <trev.norris@gmail.com> Reviewed-By: indutny - Fedor Indutny <fedor.indutny@gmail.com> Reviewed-By: bnoordhuis - Ben Noordhuis <info@bnoordhuis.nl> Amended by @rvagg to change author date from "1970-08-16 16:09:02 +0200" to "2015-08-16 16:09:02 +0200" as per discussion @ #2713
v8 will silently return an empty handle which doesn't delete our data if string length is above String::kMaxLength Fixes: #1374 PR-URL: #2402 Reviewed-By: trevnorris - Trevor Norris <trev.norris@gmail.com> Reviewed-By: indutny - Fedor Indutny <fedor.indutny@gmail.com> Reviewed-By: bnoordhuis - Ben Noordhuis <info@bnoordhuis.nl> Amended by @rvagg to change author date from "1970-08-16 16:09:02 +0200" to "2015-08-16 16:09:02 +0200" as per discussion @ #2713
v8 will silently return an empty handle which doesn't delete our data if string length is above String::kMaxLength Fixes: #1374 PR-URL: #2402 Reviewed-By: trevnorris - Trevor Norris <trev.norris@gmail.com> Reviewed-By: indutny - Fedor Indutny <fedor.indutny@gmail.com> Reviewed-By: bnoordhuis - Ben Noordhuis <info@bnoordhuis.nl> Amended by @rvagg to change author date from "1970-08-16 16:09:02 +0200" to "2015-08-16 16:09:02 +0200" as per discussion @ #2713
v8 will silently return an empty handle which doesn't delete our data if string length is above String::kMaxLength Fixes: #1374 PR-URL: #2402 Reviewed-By: trevnorris - Trevor Norris <trev.norris@gmail.com> Reviewed-By: indutny - Fedor Indutny <fedor.indutny@gmail.com> Reviewed-By: bnoordhuis - Ben Noordhuis <info@bnoordhuis.nl> Amended by @rvagg to change author date from "1970-08-16 16:09:02 +0200" to "2015-08-16 16:09:02 +0200" as per discussion @ #2713
OK everyone, @nodejs/collaborators, I've applied the heavy hand after not getting any objection here and pinging various TSC members via other channels. So heads-up, you're going to have to reset your branches to the new remote branches.
The v3.3.1-release branch is just a release proposal and the only tag we're tampering with here is one I made for v4.0.0-rc.1 that sits on the v4.0.0-rc branch which has patches I've prematurely landed just to get an RC out. I've amended the commit on each of these branches, using On the brighter side, https://github.com/nodejs/node/graphs/contributors is fixed and the history is sane once again. |
This should fix your local master (repeat for each branch, local changes will be lost):
|
@silverwind Why not just (when you're on local
? You don't need to remember any commit hash then. |
@rvagg Anything left or should this issue be closed now? |
@mzgol I think this can be closed now. Thanks for bringing this to our notice :-) |
@silverwind, not just those. #2534, for example, too. |
I am sorry to have caused so much trouble. 😞 Hope I can make it up with some pull requests 😃 |
GitHub detects one Git commit by @skomski from... 1970. This is breaking the contributors page. It was OK few months ago. Screenshot:
The text was updated successfully, but these errors were encountered: