Skip to content
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

2015-10-13, Version 4.2.1 'Argon' (LTS) Release #3337

Closed
wants to merge 1 commit into from
Closed

Conversation

jasnell
Copy link
Member

@jasnell jasnell commented Oct 13, 2015

Aiming for a quick release on Tuesday. We have two significant regressions with v4.2.0. Fixes have landed in master and v4.x. These are significant issues that affect native modules and anything using timers.

  • [b3cbd13340] - buffer: fix assertion error in WeakCallback (Fedor Indutny) #3329
  • [c245a199a7] - lib: fix undefined timeout regression (Ryan Graham) #3331

@nodejs/lts @rvagg @Fishrock123

@jasnell
Copy link
Member Author

jasnell commented Oct 13, 2015

@indutny

@indutny
Copy link
Member

indutny commented Oct 13, 2015

Let's land #3342 as well.

@trevnorris
Copy link
Contributor

@indutny I'll give 3342 a review, but doubt I'll finish before 4.2.1 needs to be released. Are those bugs critical issues, or could they wait for a week?

@jasnell
Copy link
Member Author

jasnell commented Oct 13, 2015

Ok, there are still issues with #3342 that need working out so we won't land that now. Let's document the issue in Known Issues and fix in the next patch release.

@indutny
Copy link
Member

indutny commented Oct 13, 2015

Let's report #3342 as a known issue:

Large amount of pipelined HTTP requests may cause the underlying socket to be destroyed.

* Includes fixes for two regressions
  - Assertion error in WeakCallback  - see [#3329](#3329)
  - Undefined timeout regression - see [#3331](#3331)

* Document an additional known issue with pipelined requests
  - See: #3332 and #3342
@jasnell
Copy link
Member Author

jasnell commented Oct 13, 2015

@rvagg @indutny @Fishrock123 @trevnorris ... updated to reflect status of #3342 as a known issue. Please review.

@indutny
Copy link
Member

indutny commented Oct 13, 2015

LGTM

@Fishrock123
Copy link
Contributor

No strong opinion on #3342

@trevnorris
Copy link
Contributor

LGTM

@jasnell
Copy link
Member Author

jasnell commented Oct 13, 2015

Completed.

@jasnell jasnell closed this Oct 13, 2015
Starefossen pushed a commit to Starefossen/docker-node that referenced this pull request Oct 13, 2015
PR-URL: nodejs#56
Related: nodejs/node#3337

Signed-off-by: Hans Kristian Flaatten <hans.kristian.flaatten@turistforeningen.no>
Starefossen pushed a commit to Starefossen/official-images that referenced this pull request Oct 13, 2015
PR-URL: docker-library#1120

Related: nodejs/docker-node#56 nodejs/node#3337

Signed-off-by: Hans Kristian Flaatten <hans.kristian.flaatten@turistforeningen.no>
@rvagg rvagg deleted the v4.2.1-proposal branch October 28, 2015 03:52
RichardScothern pushed a commit to RichardScothern/official-images that referenced this pull request Jun 14, 2016
PR-URL: docker-library#1120

Related: nodejs/docker-node#56 nodejs/node#3337

Signed-off-by: Hans Kristian Flaatten <hans.kristian.flaatten@turistforeningen.no>
MayaLekova added a commit to MayaLekova/node that referenced this pull request Jul 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants