Simon Giesecke
Simon Giesecke
Travis no longer (since beginning of 2019) has any IPv6 support on the amd64 machines, including the sole coverage job we currently have. Therefore, we can't see the actual coverage...
The current documentation on ZMQ_SNDHWM and ZMQ_RCVHWM deserves improvement. There has been a PR (#3041) that started work on this, which could be used as a basis.
See https://github.com/zeromq/libzmq/commit/3ca2d95bf7740d227ca56250fedf9a0f919d4f43#r28835860
Solution: add arm64 test coverage job, where ipv6 is available Also temporarily disable two zmq_socket_monitor_pipes_stats test cases that permananently fail on arm64.
When I run gren init, I get the following message: ``` $ gren init You have to run this command in a git repo folder ``` However, this *is* a...
Currently, hostname validation is done with a custom implementation, which was necessary with openssl 1.0.x. However, openssl 1.1.0 now supports this internally, but it needs to be activated as described...
The operations amqp_simple_wait_frame_noblock and amqp_socket_open_noblock are not really non-blocking operations, since they may block until the timeout is reached. amqp_simple_wait_frame_noblock can be used in a non-blocking manner, when called with...
To avoid the need for TCP loopback connections, an eventfd-like mechanism would be great that could be used with wepoll. See existing work in https://github.com/truebiker/epoll_windows/commit/32442e432b3376cb98f5c0bda5a9a0a5e832b857
It would be great to have the ability to specify additional arguments to pass to the debugger.
I tested the performance of the "old" select-based zmq_poller_poll implementation vs. the "new" WSAPoll-based zmq_poller_poll implementation on a Windows 7 x64 machine, and found the "old" select-based variant to perform...