| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
They both belong to #2430. cc @brendanashworth |
Sorry, something went wrong.
|
@thefourtheye right, thanks, there are 3 commits in here without PR-URL which is why they are showing up
is also one, I'll remove them from the list |
Sorry, something went wrong.
|
@rvagg misspolling in second sentence
|
Sorry, something went wrong.
|
Is the comment on known issue:
still true, given @bnoordhuis's fix (#2620) landed here? I couldn't actually find a reference to process.send in process.markdown. Am I looking in the wrong spot? |
Sorry, something went wrong.
|
OK, my mistake; this is actually related to child.send in child_process.markdown. Ignore my last question on docs. Known issue commentary query stands. |
Sorry, something went wrong.
|
I thought the process.send known issue was removed but I was mistaken, fixed now, thanks |
Sorry, something went wrong.
It can be cleared off the known issues list though. The documentation for process.send() at all is a different issue, and would be fixed by #1978. |
Sorry, something went wrong.
I think link should be changed into confirmed-bug Issues with confirmed bugs. . |
Sorry, something went wrong.
Good catch. There's a few more in that changelog, I think an s/\/io\.js/\/node/g is in order. |
Sorry, something went wrong.
|
@silverwind I wouldn't do that; it will mess up the notable change for #2367. |
Sorry, something went wrong.
|
fixed for this release, I think I'm content to leave the others as they are but if someone wants to PR a big change and debate it then you're welcome to do so |
Sorry, something went wrong.
|
Another commit missing PR-URL, my fault
|
Sorry, something went wrong.
|
C-ares tests are showing some flakiness on the unstable WiFi here at
|
Sorry, something went wrong.
There was a problem hiding this comment.
Perhaps you can s/io.js/nodejs/ on the URLs in this block?
Sorry, something went wrong.
This list of changes is relative to the last io.js v3.x branch release, v3.3.0. Please see the list of notable changes in the v3.x, v2.x and v1.x releases for a more complete list of changes from 0.12.x. Note, that some changes in the v3.x series as well as major breaking changes in this release constitute changes required for full convergence of the Node.js and io.js projects. * child_process: ChildProcess.prototype.send() and process.send() operate asynchronously across all platforms so an optional callback parameter has been introduced that will be invoked once the message has been sent, i.e. .send(message[, sendHandle][, callback]) (Ben Noordhuis) #2620. * node: Rename "io.js" code to "Node.js" (cjihrig) #2367. * node-gyp: This release bundles an updated version of node-gyp that works with all versions of Node.js and io.js including nightly and release candidate builds. From io.js v3 and Node.js v4 onward, it will only download a headers tarball when building addons rather than the entire source. (Rod Vagg) #2700. * npm: Upgrade to version 2.14.2 from 2.13.3, includes a security update, see https://github.com/npm/npm/releases/tag/v2.14.2 for more details, (Kat Marchán) #2696. * timers: Improved timer performance from porting the 0.12 implementation, plus minor fixes (Jeremiah Senkpiel) #2540, (Julien Gilli) nodejs/node-v0.x-archive#8751 nodejs/node-v0.x-archive#8905 * util: The util.is*() functions have been deprecated, beginning with deprecation warnings in the documentation for this release, users are encouraged to seek more robust alternatives in the npm registry, (Sakthipriyan Vairamani) #2447. * v8: Upgrade to version 4.5.103.30 from 4.4.63.30 (Ali Ijaz Sheikh) #2632. - Implement new TypedArray prototype methods: copyWithin(), every(), fill(), filter(), find(), findIndex(), forEach(), indexOf(), join(), lastIndexOf(), map(), reduce(), reduceRight(), reverse(), slice(), some(), sort(). See https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/TypedArray for further information. - Implement new TypedArray.from() and TypedArray.of() functions. See https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/TypedArray for further information. - Implement arrow functions. See https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Functions/Arrow_functions for further information. - Full ChangeLog available at https://github.com/v8/v8-git-mirror/blob/4.5.103/ChangeLog
|
LGTM as long as the commits list is good. |
Sorry, something went wrong.
|
Also did not check any of the links. |
Sorry, something went wrong.
|
LGTM. Testing on the unreliable wifi here has brought up a potential npm issue that I'm still investigating but ecosystem tests using citgm are looking good so far on both Mac OSX and Windows. |
Sorry, something went wrong.
|
LGTM |
Sorry, something went wrong.
|
Pile-on LGTM. |
Sorry, something went wrong.
|
Let's not forget the CHANGELOG.md update in master :) |
Sorry, something went wrong.
Sorry, something went wrong.
|
Interesting development .. this has been running since the 4.0.0 release and memory usage just jumped for no good reason (the server has been left alone doing the same thing over and over) Code is here: https://github.com/rvagg/node-memtest/blob/master/test/http-spew/index.js Is it worth pinging someone in the V8 team to try and understand this? |
Sorry, something went wrong.
|
@rvagg Would it be possible to run http-spew with --trace_fragmentation --trace_fragmentation_verbose --track_gc_object_stats --trace_gc_object_stats --trace_gc --trace_gc_nvp --trace_gc_verbose? It's going to log a stupendous amount of info so you probably want to redirect stdout to the syslog. If it's a debug build, --check_handle_count --code_stats --print_handles --print_global_handles --verify_heap would be good to have too. |
Sorry, something went wrong.
|
that might be a bit much for this little machine I'm running these on, if the log data is going to spew what would I actually be looking for? would it be obvious or would I need to trace back to the moment when the spike occurred? |
Sorry, something went wrong.
|
And back down again we go. Even though it's setInterval() triggering this work and crypto.randomBytes() is involved I'm pretty sure this is not about having overlapping/backed up work, this is a V8 thing. / @ChALkeR |
Sorry, something went wrong.
I'd expect something to change around the time of the swings, maybe more frequent gc'ing or log messages about exceeding some threshold or heuristic. At the very least, you should see it in the verbose summary that's printed with every sweep (assuming it's actually V8 and not node.) |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
2015-09-08, Version 4.0.0 (Stable), @rvagg
Notable changes
This list of changes is relative to the last io.js v3.x branch release, v3.3.0. Please see the list of notable changes in the v3.x, v2.x and v1.x releases for a more complete list of changes from 0.12.x. Note, that some changes in the v3.x series as well as major breaking changes in this release constitute changes required for full convergence of the Node.js and io.js projects.
Known issues
See confirmed-bug Issues with confirmed bugs. for complete and current list of known issues.
Commits