kc3-lang/libevent
Branch :
Log
| Author | Commit | Date | CI | Message |
|---|---|---|---|---|
 |
4294867c | 2016-07-06 12:21:38 | Bump version to 2.0.23-beta Tested on: - arch linux (openssl 1.0) - ubuntu (https://travis-ci.org/libevent/libevent/branches patches-2.0) - freebsd (libevent-extras in vagrant) - osx (libevent-extras in vagrant) Refs: #744 | |
 |
9a88d75c | 2019-01-20 19:55:59 | Release notes for 2.0.23-beta [ Based on commit c87a0680 ] | |
|
2f656ffb | 2019-01-20 22:40:57 | test/buffer: write >GETPIPE_SZ via events over pair to avoid stall [ Upstream commit 0aad01436af27c5807d48701028020bb51cba387 ] | |
|
4300faad | 2019-01-20 19:53:11 | Update ACKNOWLEDGMENTS section for 2.0.23-beta | |
 |
70a39d45 | 2018-10-31 00:09:38 | Cover ET with multiple events for same fd [ Upstream commit 77c0e510581b88242d7d7bcff4954cedc5613554 ] Refs: #636 | |
 |
d22efeb1 | 2018-02-23 19:01:03 | bufferevent_socket_connect{,_hostname}() missing event callback and use ret code [ Upstream commit f7bc1337977553f5f966f13840a5f7feba2d0bd5 ] - When socket() failed in bufferevent_socket_connect() , the event callback should be called also in bufferevent_socket_connect_hostname(). eg. when use bufferevent_socket_connect_hostname() to resolve and connect an IP address but process have a smaller ulimit open files, socket() fails always but caller is not notified. - When make socket nonblocking failed in bufferevent_socket_connect(), free the fd. - Make bufferevent_socket_connect()'s behavior more consistent: function return error then no callback, function return ok then error passed by event callback. Backport-for: 2.0 Refs: #597 Refs: #599 Refs: #600 Closes: #599 (cherry-pick) | |
|
d1487831 | 2018-10-30 23:59:24 | Preserve ET bit for backends with changelist [ Upstream commit a1293bd2e626cba1f687cd0e50a219f8661775fc ] Fixes: #636 | |
|
63306e6f | 2018-10-30 08:50:08 | Epoll ET setting lost with multiple events for same fd [ Upstream commit b77d3e787b5522380c65838d3baa22e661eff0db ] After two or more events have been registered for the same file descriptor using EV_ET, if one of the events is deleted, then the epoll_ctl() call issued by libevent drops the EPOLLET flag resulting in level triggered notifications. [ azat: test for EV_ET for EPOLL_CTL_MOD too, for libevent 2.0 ] Fixes: #636 | |
 |
a8a315ec | 2014-06-13 14:18:13 | ignore config.cache/test-driver files [ Upstream commit c83f3333a34251275c38878e9667c904a485ac6d ] config.cache is generated when you run `./configure -C`. test-driver comes from newer autotools. | |
 |
db6c5dfb | 2013-05-16 16:38:39 | If evsel->del() fails, don't leave the evmap in an inconsistent state. [ Upstream commit 9b5a527f5bf898250a797dde59cadb4f64e8967a ] This fixes assertion failures in cases where epoll() fails with EBADF -- the root cause for which is as of yet unknown. It seems something (OpenSSL?) is closing the file descriptor under our feet. |