#
e19089f7 |
| 24-Feb-2015 |
Fedor Indutny |
stream: use SO_OOBINLINE on OS X In the collaboration with Ben Noordhuis <info@bnoordhuis.nl> and Saúl Ibarra Corretgé <saghul@gmail.com>. Reviewed-By: Saúl Ibarra Corretgé <sag
stream: use SO_OOBINLINE on OS X In the collaboration with Ben Noordhuis <info@bnoordhuis.nl> and Saúl Ibarra Corretgé <saghul@gmail.com>. Reviewed-By: Saúl Ibarra Corretgé <saghul@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
show more ...
|
#
b36d4ff9 |
| 09-Feb-2015 |
Ben Noordhuis |
unix: implement uv_stream_set_blocking() Commit 393c1c5 ("unix: set non-block mode in uv_{pipe,tcp,udp}_open") causes a regression in the io.js cluster module. The io.js documen
unix: implement uv_stream_set_blocking() Commit 393c1c5 ("unix: set non-block mode in uv_{pipe,tcp,udp}_open") causes a regression in the io.js cluster module. The io.js documentation states that `worker.send()` and `process.send()` are synchronous but they no longer were after upgrading to libuv v1.2.1. The reason they are synchronous is because of backpressure - or rather, lack of backpressure: a slow consumer eventually causes a fast producer to run out of memory because the backlog of pending messages in the producer can grow unchecked. Ergo, implement uv_stream_set_blocking() on UNIX platforms to let io.js enable the old blocking behavior for pipes again. Refs: https://github.com/iojs/io.js/issues/760 PR-URL: https://github.com/libuv/libuv/pull/187 Reviewed-By: Saúl Ibarra Corretgé <saghul@gmail.com>
show more ...
|
Revision tags: v1.3.0, v0.10.33 |
|
#
965fffc2 |
| 23-Jan-2015 |
Ben Noordhuis |
build: compile -D_GNU_SOURCE on linux Fixes a number of -Wimplicit-function-declaration warnings for functions that are behind _GNU_SOURCE on old systems, like strndup() and pread().
build: compile -D_GNU_SOURCE on linux Fixes a number of -Wimplicit-function-declaration warnings for functions that are behind _GNU_SOURCE on old systems, like strndup() and pread(). PR-URL: https://github.com/libuv/libuv/pull/162 Reviewed-By: Saúl Ibarra Corretgé <saghul@gmail.com>
show more ...
|
Revision tags: v1.2.1 |
|
#
434ce034 |
| 06-Jan-2015 |
Johan Bergström |
build: make dist now generates a full tarball Autotools tries to figure out what's necessary to create a tarball through included files in Makefile.am. Since libuv has conditionals based
build: make dist now generates a full tarball Autotools tries to figure out what's necessary to create a tarball through included files in Makefile.am. Since libuv has conditionals based on target OS as well as additional samples/documentation, extra_files needs to include these. Also, add the result of make dist to gitignore. PR-URL: https://github.com/libuv/libuv/pull/118 Reviewed-By: Saúl Ibarra Corretgé <saghul@gmail.com>
show more ...
|
Revision tags: v1.2.0, v0.10.32 |
|
#
e6e871ac |
| 05-Jan-2015 |
Ben Noordhuis |
build: move flags from Makefile.am to configure.ac Move compile-time flags that are not platform-specific defines to configure.ac where they can be properly feature-detected. PR
build: move flags from Makefile.am to configure.ac Move compile-time flags that are not platform-specific defines to configure.ac where they can be properly feature-detected. PR-URL: https://github.com/libuv/libuv/pull/24 Reviewed-By: Saúl Ibarra Corretgé <saghul@gmail.com>
show more ...
|
#
751ac48b |
| 25-Dec-2014 |
Ben Noordhuis |
linux: fix epoll_pwait() sigmask size calculation Revisit the fix from commit b705b53. The problem with using sigset_t and _NSIG is that the size of sigset_t and the value of _NSIG depe
linux: fix epoll_pwait() sigmask size calculation Revisit the fix from commit b705b53. The problem with using sigset_t and _NSIG is that the size of sigset_t and the value of _NSIG depend on what headers libuv picks up first, <signal.h> or <asm/signal.h>. With the former, sizeof(sigset_t) = 128; with the latter, it's 8. Simply sidestep the issue by calculating the signal mask as a 64 bits integer, without using sigset_t or _NSIG. PR-URL: https://github.com/libuv/libuv/pull/83 Reviewed-By: Saúl Ibarra Corretgé <saghul@gmail.com>
show more ...
|
Revision tags: v1.1.0, v0.10.31 |
|
#
3ccd95ec |
| 16-Dec-2014 |
John Marino |
build: fix dragonflybsd autotools build Fixes multiple definition linker errors due to what seems to be multiple inclusions of src/unix/freebsd.c and src/unix/kqueue.c. Fixes #7
build: fix dragonflybsd autotools build Fixes multiple definition linker errors due to what seems to be multiple inclusions of src/unix/freebsd.c and src/unix/kqueue.c. Fixes #72, refs joyent/libuv#1576. PR-URL: https://github.com/libuv/libuv/issues/72 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
show more ...
|
#
4203ef20 |
| 14-Dec-2014 |
Luis Lavena |
win: fix autotools build of tests Add missing test file to match GYP definition and solve undefined reference. PR-URL: https://github.com/libuv/libuv/pull/69 Reviewed-By: Be
win: fix autotools build of tests Add missing test file to match GYP definition and solve undefined reference. PR-URL: https://github.com/libuv/libuv/pull/69 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
show more ...
|
Revision tags: v1.0.2, v0.10.30, v1.0.1, v1.0.0 |
|
#
cb514002 |
| 06-Nov-2014 |
Ben Noordhuis |
build: remove dtrace probes The existing probes, all two of them, cause a great deal of pain for people trying to build libuv on Linux because of SystemTap's dtrace(1) utilitity not
build: remove dtrace probes The existing probes, all two of them, cause a great deal of pain for people trying to build libuv on Linux because of SystemTap's dtrace(1) utilitity not understanding the -xnolibs flag. We could hack around that but it's easier to just remove the probes: they are largely useless and unused while still needing a lot of supporting infrastructure. This commit removes 200 lines of code and configuration. Refs joyent/libuv#1478.
show more ...
|
Revision tags: v0.10.29, v1.0.0-rc2 |
|
#
59658a8d |
| 05-Oct-2014 |
Tomasz Kołodziejski |
unix, windows: add uv_thread_equal |
#
3193b67f |
| 26-Sep-2014 |
Robin Hahling |
build: add DragonFly BSD support in autotools |
#
1cc25170 |
| 20-Sep-2014 |
Rob Adams |
build: add missing fixtures to distribution tarball |
Revision tags: v1.0.0-rc1 |
|
#
5ccdfc56 |
| 08-Sep-2014 |
Saúl Ibarra Corretgé |
test: add test for closing and recreating default loop |
#
145b76b8 |
| 07-Sep-2014 |
Fedor Indutny |
darwin: allocate enough space for select() hack `fd_set`s are way too small for `select()` hack when stream's fd is bigger than 1023. Make `fd_set`s a part of `uv__stream_select_t` s
darwin: allocate enough space for select() hack `fd_set`s are way too small for `select()` hack when stream's fd is bigger than 1023. Make `fd_set`s a part of `uv__stream_select_t` structure. fix #1461
show more ...
|
#
e524f89b |
| 29-Aug-2014 |
Saúl Ibarra Corretgé |
core: update version to 1.0.0 |
#
6941cab5 |
| 27-Aug-2014 |
Bert Belder |
windows: fix buffer leak after failed udp send Fixes #1426 Signed-off-by: Saúl Ibarra Corretgé <saghul@gmail.com> |
#
4ca9a363 |
| 22-Aug-2014 |
Saúl Ibarra Corretgé |
unix, windows: add uv_fileno Returns the platform specific file descriptor for handles that are backed by one. The datatype is abstracted as uv_os_fd_t, which maps to int on Unices a
unix, windows: add uv_fileno Returns the platform specific file descriptor for handles that are backed by one. The datatype is abstracted as uv_os_fd_t, which maps to int on Unices and HANDLE on Windows. Users can use this function to set specific socket options, for example, in a non portable way. This function is essentially a shotgun, you better be careful with whatever you do with it, don't blame me if you used it to get the fd of a stream, close it yourself and expect things to Just Work.
show more ...
|
#
bd0692e6 |
| 24-Aug-2014 |
Saúl Ibarra Corretgé |
build: use same CFLAGS in autotools build as in gyp Closes #1362 |
#
d5e6f437 |
| 21-Aug-2014 |
Andrius Bentkus |
unix: fix tcp write after bad connect freezing If the connect wouldn't go off (no such tcp remote or any other failure), the subsequent writes made would not be called. Now we call the w
unix: fix tcp write after bad connect freezing If the connect wouldn't go off (no such tcp remote or any other failure), the subsequent writes made would not be called. Now we call the writes in the queue with ECANCELED if the connect fails. Fix #1432
show more ...
|
Revision tags: v0.11.29 |
|
#
15521842 |
| 14-Aug-2014 |
Julien Gilli |
unix: read on stream even when UV__POLLHUP set. This fixes a SmartOS specific issue that happens when reading from a stream that is the reading end of a pipe that has been closed by
unix: read on stream even when UV__POLLHUP set. This fixes a SmartOS specific issue that happens when reading from a stream that is the reading end of a pipe that has been closed by the parent process. In this case, a UV__POLLHUP event would be set on the stream and would prevent the event loop from closing it. As a result, the event loop would think there are stil handles open, and leave the process hanging. Fixes #1419.
show more ...
|
Revision tags: v0.11.28, v0.11.27, v0.10.28 |
|
#
0ecee213 |
| 07-Jul-2014 |
Andrius Bentkus |
unix, windows: add uv_recv_buffer_size and uv_send_buffer_size |
Revision tags: v0.11.26, v0.10.27, v0.11.25 |
|
#
cdc979db |
| 23-Apr-2014 |
Andrew Low |
aix: improve AIX compatibility |
#
960eefb3 |
| 06-Jul-2014 |
Andrius Bentkus |
unix: guarantee write queue cb execution order in streams The problem was that the canceled write callbacks were being called before the already written callbacks, even though they w
unix: guarantee write queue cb execution order in streams The problem was that the canceled write callbacks were being called before the already written callbacks, even though they were queued after them.
show more ...
|
#
817c0925 |
| 11-Jul-2014 |
Saúl Ibarra Corretgé |
unix: remove incorrect assert After 41891222bc landed it's possible that uv__udp_sendmsg is called even if there are no pending write nor write completed requests: 1. User calls
unix: remove incorrect assert After 41891222bc landed it's possible that uv__udp_sendmsg is called even if there are no pending write nor write completed requests: 1. User calls uv_udp_send and the request is sent immediately. The request is the added to the completed queue and we 'feed' the uv__io handle so that we process the completed request in the next iteration. 2. User calls uv_udp_send again but the request is not completed immediately, so it's queued in the write_queue. 3. The uv__io handle gets a UV__POLLOUT event and uv__udp_sendmsg is run, which completes the send request and puts it in the write_completed_queue. Afterwards, uv__udp_run_completed is executed and the write_completed queue is drained. 4. At this point, the uv__io handle was made pending in step 3, in uv__udp_sendmsg, but we no longer have requests to write or to complete, so we skip processing.
show more ...
|
#
0d43992c |
| 29-Jun-2014 |
Andrius Bentkus |
unix, win: add uv_udp_try_send The function returns UV_EAGAIN if the queue is not empty and the message couldn't be sent immediately. |