Skip to content

Conversation

@sodabrew
Copy link
Member

No description provided.

@sodabrew sodabrew added this to the v1.2.6 milestone Apr 30, 2018
sodabrew and others added 9 commits April 30, 2018 02:19
The unbind callback absolutely must not raise an exception or the reactor will crash.
If there is no EM.error_handler, or if the error_handler retrows, then stop the reactor,
stash the exception in $wrapped_exception, and the exception will be raised after the
reactor is cleaned up (see the last line of self.run).

This fixes many crash reports in the 1.2 series since eventmachine#327 was merged.
…or (eventmachine#801)

This method exists in the cpp version but not in the pure ruby version. When
there is an undelivered message for example, it will attempt to check the socket
status and fail saying that the method report_connection_error_status does not
exist. This is in turn causes the connection to fail. It will not return the
socket status.
@sodabrew sodabrew force-pushed the release-1.2.6 branch 2 times, most recently from 454ecbd to b7d3685 Compare April 30, 2018 09:44
…tmachine#831)

This resolves the conflict of socket bind() vs std::bind(), as more
std:: functions may be introduced in future versions of C++.

Resolves eventmachine#830
@sodabrew sodabrew merged commit 159ad95 into eventmachine:1.2-stable Apr 30, 2018
@sodabrew sodabrew deleted the release-1.2.6 branch April 30, 2018 10:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants