lukechilds/node - node - Gitea: Git with a cup of tea

Commit Graph

Author	SHA1	Message	Date
Fedor Indutny	d6fd118727	deps: update openssl to 1.0.1g	11 years ago
Fedor Indutny	962f96d341	deps: update libuv to v0.11.23	11 years ago
Ben Noordhuis	5e24adbb90	deps: fix up v8 postmortem codegen Fix up overzealous parses, strip whitespace from class and field names.	11 years ago
Ben Noordhuis	67e078094b	deps: upgrade v8 to 3.25.30	11 years ago
Trevor Norris	8d6fa72d97	v8: upgrade to 3.24.35.22	11 years ago
dcarney@chromium.org	85d595c8c2	deps: apply floating patch to v8 Original commit message below: fix FunctionCallbackInfo ambiguity - when compiling tools that embed v8 with g++ FunctionCallbackInfo is currently ambigous - more info: https://github.com/joyent/node/issues/7337 - original patch is here: https://codereview.appspot.com/78770045/ TBR=svenpanne@chromium.org Review URL: https://codereview.chromium.org/201573012 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@20217 ce2b1a6d-e550-0410-aec6-3dcde31c8c00	11 years ago
isaacs	bd547d6598	npm: upgrade to 1.4.6 * Documentation upgrades * Fix glob bug which prevents proper README publishing * node-gyp upgrade to 0.13 * Documentation updates * Add --save-exact to save an exact dep (instead of a range) * alias 't' to 'test'	11 years ago
Fedor Indutny	4d140746f0	deps: update v8 to 3.24.35.17	11 years ago
Fedor Indutny	0c5a0ecc7c	deps: allow allocations in gc epilogue/prologue See https://codereview.chromium.org/177243012/	11 years ago
Fedor Indutny	030d03190f	deps: backport a6fed7c5 from v8's trunk	11 years ago
Fedor Indutny	1c7bf245dc	deps: update v8 to 3.24.40	11 years ago
Bryan Cantrill	e496707d39	mdb_v8: update to latest version * ::jsstack -v prints function defintion * ::jsprint works with objects with only numeric properties * update tests to use builtin mdb_v8 * add more symbols to postmortem script - pending upstream inclusion	11 years ago
Timothy J Fontaine	e92d35d80b	uv: Upgrade to v0.11.22	11 years ago
Ben Noordhuis	6bd78fd770	deps: fix v8 valgrind warning Fix the following valgrind warning: Conditional jump or move depends on uninitialised value(s) at 0x7D64E7: v8::internal::GlobalHandles::IterateAllRootsWithClassIds(v8::internal::ObjectVisitor*) (global-handles.cc:613) by 0x94DCDC: v8::internal::NativeObjectsExplorer::FillRetainedObjects() (profile-generator.cc:2849) # etc. This was fixed upstream in r12903 and released in 3.15.2 but that commit was never back-ported to the 3.14 branch that node.js v0.10 uses. The code itself works okay; this commit simply shuffles the clauses in an `if` statement to check that the node is in use before checking its class id (which is uninitialized if the node is not in use.)	11 years ago
Timothy J Fontaine	cd08c8a0e5	uv: Upgrade to v0.11.21	11 years ago
Timothy J Fontaine	c2aea3747d	uv: Upgrade to v0.10.25	11 years ago
isaacs	217bb0c964	npm: upgrade to 1.4.3	11 years ago
Ben Noordhuis	3421d29d63	v8: unbreak freebsd build reland `de8c0a5` Fixes #7020 and #7021	11 years ago
isaacs	55543d3c45	npm: Upgrade to v1.4.0 - Removes 'npm publish -f' - Documentation - Bug-fixes - Update license etc to refer to npm, Inc. rather than @isaacs personally	11 years ago
isaacs	2e8bb57fe3	npm: upgrade to 1.3.26	11 years ago
Alexis Campailla	15de8c2b60	openssl: fix keypress requirement in apps on win32 Re-applying commit `153784b348`, which was overwritten by the update to openssl 1.0.1f. Original source: http://openssl.6102.n7.nabble.com/PATCH-s-client-Fix-keypress-requirement-with-redirected-input-on-Windows-td46787.html	11 years ago
Fedor Indutny	fac8f396cc	deps: backport 883637bd from latest v8 Original commit message: VS2013 contains a number of improvements, most notably the addition of all C99 math functions. I'm a little bit concerned about the change I had to make in cpu-profiler.cc, but I spent quite a bit of time looking at it and was unable to figure out any rational explanation for the warning. It's possible it's spurious. Since it seems like a useful warning in general though, I chose not to disable globally at the gyp level. I do think someone with expertise here should probably try to determine if this is a legitimate warning. BUG=288948 R=dslomov@chromium.org Review URL: https://codereview.chromium.org/23449035 NOTE: Path applied without `cpu-profiler.cc` changes because in our version it was looking totally different.	11 years ago
Timothy J Fontaine	95b8a75d5e	v8: Upgrade to 3.22.24.19	11 years ago
Fedor Indutny	597eb6a5ae	deps: update http_parser to 2.2.1 Main changes: * Fixed content-length and chunk-size overflow test	11 years ago
Fedor Indutny	64d33a7519	deps: update uv to 0.11.18	11 years ago
Fedor Indutny	896e19330a	deps: backport b5135bbc from c-ares repo Original commit message: ares_parse_txt_reply: return a ares_txt_reply node for each sub-string Previously, the function would wrongly return all substrings merged into one. fix #6931	11 years ago
isaacs	485fcf9c63	npm: Upgrade to v1.3.25	11 years ago
Trevor Norris	f78e5df854	v8: upgrade to 3.22.24.17	11 years ago
Timothy J Fontaine	8b7ec73331	uv: Upgrade to v0.10.23	11 years ago
isaacs	f645c40fcd	npm: Upgrade to v1.3.24	11 years ago
svenpanne@chromium.org	196184d332	v8: backport codereview.chromium.org/11362182 Keep the number of descriptors below DescriptorArray::kMaxNumberOfDescriptors even for accessors Review URL: https://codereview.chromium.org/11362182	12 years ago
Fedor Indutny	4800310f6a	deps: fix openssl assembly error on ia32 win32 `x86masm.pl` was mistakenly using .486 instruction set, why `cpuid` (and perhaps others) are requiring .686 .	11 years ago
Fedor Indutny	390598608c	deps: update openssl to 1.0.1f	11 years ago
Timothy J Fontaine	30b3bc2f7c	uv: Upgrade to v0.10.22	11 years ago
isaacs	1be9365930	npm: Upgrade to 1.3.23	11 years ago
Fedor Indutny	92b6417098	crypto: introduce .setEngine(engine, [flags])	11 years ago
Timothy J Fontaine	5ce4f3ec3d	v8: Upgrade to 3.22.24.10	11 years ago
Timothy J Fontaine	8590f810a5	uv: Upgrade to v0.11.17	11 years ago
isaacs	7f82faee30	npm: Upgrade to v1.3.22	11 years ago
Fedor Indutny	a35a2f0192	deps: update http_parser to 2.2 Main changes: * Added support for http statusMessage	11 years ago
Fedor Indutny	2394b974cc	deps: v8 apply temporary fix until backport Fix node.js debug build with a temporary v8 fix until the v8 team will backport the fix from the more recent version of v8. see https://code.google.com/p/v8/issues/detail?id=3062	11 years ago
Timothy J Fontaine	9371be0aa1	uv: Upgrade to v0.10.21	11 years ago
Ben Noordhuis	2eaef9f6da	cluster, v8: fix --logfile=%p.log The %p is replaced with the current PID. This used to work in node.js v0.9.7 but it seems to have been lost somewhere along the way. This commit makes the fix from `6b713b52` ("cluster: make --prof work for workers") work again. Without it, all log data ends up in a single file and is unusable because the addresses are all wrong.	11 years ago
isaacs	2a741f2d12	npm: upgrade to 1.3.21	11 years ago
isaacs	e10c223eb6	npm: upgrade to 1.3.20 The 1.3.19 release had a critical bug: any packages published with it could not be installed, because the shasum would be incorrect. Thankfully, 1.3.19 was published using 1.3.19, so could not be installed by any users! However, if it goes out as part of a Node.js release, then obviously that would be a problem.	11 years ago
isaacs	97738994e0	npm: Upgrade to 1.3.19	11 years ago
Fedor Indutny	8803aa3af7	deps: update v8 to 3.22.24.9	11 years ago
jkummerow@chromium.org	39e2426b20	v8: backport fix for CVE-2013-{6639\|6640} Quoting CVE-2013-6639: The DehoistArrayIndex function in hydrogen-dehoist.cc in Google V8 before 3.22.24.7, as used in Google Chrome before 31.0.1650.63, allows remote attackers to cause a denial of service (out-of-bounds write) or possibly have unspecified other impact via JavaScript code that sets the value of an array element with a crafted index. Quoting CVE-2013-6640: The DehoistArrayIndex function in hydrogen-dehoist.cc in Google V8 before 3.22.24.7, as used in Google Chrome before 31.0.1650.63, allows remote attackers to cause a denial of service (out-of-bounds read) via JavaScript code that sets a variable to the value of an array element with a crafted index. Like 6b92a7, this is unlikely to affect node.js because it only runs local, trusted code. However, if there exists some module somewhere that populates an array index with remotely provided data this could very well be used to crash a remote server running node. Defense in depth and all. This is a backport of upstream commit r17801. Original commit log: Limit size of dehoistable array indices LOG=Y BUG=chromium:319835,chromium:319860 R=dslomov@chromium.org Review URL: https://codereview.chromium.org/74113002	11 years ago
Fedor Indutny	f61d9405bf	uv: Upgrade to v0.11.16	11 years ago
Timothy J Fontaine	910bc3c02d	uv: Upgrade v0.10.20	11 years ago

1 2 3 4 5 ...

1282 Commits (de7c0e8c021a4cce9be0e6e6a63d42455109ba94)