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

Commit Graph

Author	SHA1	Message	Date
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
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
Timothy J Fontaine	30b3bc2f7c	uv: Upgrade to v0.10.22	11 years ago
isaacs	1be9365930	npm: Upgrade to 1.3.23	11 years ago
isaacs	7f82faee30	npm: Upgrade to v1.3.22	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
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
Timothy J Fontaine	910bc3c02d	uv: Upgrade v0.10.20	11 years ago
isaacs	a22de4f7ee	npm: Upgrade to 1.3.17	11 years ago
isaacs	c1452f4c6f	npm: Upgrade to v1.3.15	11 years ago
Timothy J Fontaine	ac799ba0af	uv: Upgrade to v0.10.19	11 years ago
yangguo@chromium.org	007393a09d	v8: use correct timezone information on Solaris `timezone` variable contains the difference, in seconds, between UTC and local standard time (see `man 3 localtime` on Solaris). Call to `tzset` is required to apply contents of `TZ` variable to `timezone` variable. BUG=v8:2064 Review URL: https://chromiumcodereview.appspot.com/10967066 Patch from Maciej Małecki <me@mmalecki.com>. This is a back-port of upstream commit r12802 and a forward port of commit `9fa953d` from the v0.8 branch. V8 3.22 in the master branch contains the patch so no further forward-porting is necessary.	12 years ago
Ben Noordhuis	3dcc9b93e1	v8: unbreak `make native` build The security fix from commit `6b92a713` also back-ported the test case. Said test case relies on API that is only available in newer versions of V8 and, as a result, broke the `make native` and `make <arch.mode>` builds. This commit reverts that part of the back-port. Fixes the following build error: ../test/cctest/test-api.cc: In function ‘void TestRegress260106()’: ../test/cctest/test-api.cc:17712:34: error: ‘class v8::Context’ has no member named ‘GetIsolate’	11 years ago
isaacs	8f221bc43d	npm: Upgrade to 1.3.14	11 years ago
isaacs	4b5e6a38df	npm@1.3.13	11 years ago
isaacs	f6f176e108	npm@1.3.12	11 years ago
Timothy J Fontaine	8fc48bcf4c	uv: Upgrade to v0.10.18	11 years ago
Timothy J Fontaine	55546f55d4	uv: Upgrade to v0.10.17	11 years ago
isaacs	ebeae2df51	npm: upgrade to 1.3.11	11 years ago
isaacs	1be09dfc25	npm: upgrade to v1.3.10	11 years ago
Bert Belder	6301613ff5	uv: upgrade to v0.10.16	11 years ago
Bert Belder	5508236c49	uv: update to v0.10.15	11 years ago
Timothy J Fontaine	e445fbda1f	uv: Upgrade v0.10.14	11 years ago
Ben Noordhuis	8d42c6344b	deps: upgrade http_parser to 303c4e4 Upgrade to joyent/http-parser@303c4e4. Changes: * Do not accept PUN/GEM methods as PUT/GET. * Further request method check strengthening.	11 years ago
isaacs	5abdef790c	npm: Upgrade to 1.3.8	11 years ago
mstarzinger@chromium.org	6b92a71321	v8: back-port fix for CVE-2013-2882 Quoting the CVE: Google V8, as used in Google Chrome before 28.0.1500.95, allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors that leverage "type confusion." Likely has zero impact on node.js because it only runs local, trusted code but let's apply it anyway. This is a back-port of upstream commit r15665. Original commit log: Use internal array as API function cache. R=yangguo@chromium.org BUG=chromium:260106 TEST=cctest/test-api/Regress260106 Review URL: https://codereview.chromium.org/19159003 Fixes #5973.	11 years ago
isaacs	bea9dfa14c	npm: Upgrade to 1.3.7	11 years ago
Timothy J Fontaine	5c81f41e70	uv: Upgrade to v0.10.13	11 years ago
isaacs	ff0de45929	npm: Upgrade to v1.3.5	11 years ago
isaacs	5e86519199	npm: Upgrade to 1.3.4	11 years ago
isaacs	ff8a4058bf	npm: Upgrade to 1.3.3	11 years ago
isaacs	8bac8857f5	uv: Upgrade to v0.10.12	11 years ago
isaacs	f5602bda18	npm: Upgrade to 1.3.2	11 years ago
isaacs	9195455637	npm: Upgrade to 1.2.32	12 years ago
Ben Noordhuis	41fc46e52f	v8: add setVariableValue debugger command Issue 2399 part 1: In debugger allow modifying local variable values Issue 2399 part 2: In debugger allow modifying local variable values Review URL: https://codereview.chromium.org/11415042 Review URL: https://codereview.chromium.org/11412310 This is a back-port of upstream svn commits r13122 and r13202.	12 years ago
Andrei Sedoi	cc517497e6	v8: fix build for mips32r2 architecture This is a floating patch as a backport from v8 3.15.0 Committed: https://code.google.com/p/v8/source/detail?r=12833	12 years ago
Andrei Sedoi	884b25356f	openssl: add missing configuration pieces for MIPS	12 years ago
Ben Noordhuis	48476273eb	uv: upgrade to 0.10.11	12 years ago
isaacs	49d9ad9d81	npm: Upgrade to 1.2.30	12 years ago
Trevor Norris	5d4ac272c7	v8: fix pointer arithmetic undefined behavior Clang branch release_33 would optimize out a != NULL check because of some undefined behavior. This is a floating patch as a backport of that fix. Committed: http://code.google.com/p/v8/source/detail?r=13570	12 years ago
isaacs	4d13fcf481	npm: Upgrade to 1.2.27	12 years ago
isaacs	96c30df10c	uv: Upgrade to 0.10.10	12 years ago
isaacs	f28f67cf75	npm: Upgrade to 1.2.25	12 years ago

1 2 3 4 5 ...

1141 Commits (a98d541733336aa1e804e8397bf4e202a7150473)