Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Upgrade to OpenSSL 0.9.x #59

Closed
wants to merge 19 commits into from
Closed

Upgrade to OpenSSL 0.9.x #59

wants to merge 19 commits into from

Commits on Nov 11, 2017

  1. Update to openssl 0.9.x

    @grahamc
    grahamc committed Nov 11, 2017
    Configuration menu
    Copy the full SHA
    7c9249c View commit details
    Browse the repository at this point in the history

  2. well, it compiles?

    @grahamc
    grahamc committed Nov 11, 2017
    Configuration menu
    Copy the full SHA
    91d5b56 View commit details
    Browse the repository at this point in the history

Commits on Nov 12, 2017

  1. So it seems to work? Not great though

    @grahamc
    grahamc committed Nov 12, 2017
    Configuration menu
    Copy the full SHA
    0017208 View commit details
    Browse the repository at this point in the history

  2. Remove locking and unnecessary references

    @grahamc
    grahamc committed Nov 12, 2017
    Configuration menu
    Copy the full SHA
    1216885 View commit details
    Browse the repository at this point in the history

Commits on Dec 2, 2017

  1. Update connection.rs

    @grahamc
    grahamc authored Dec 2, 2017
    Configuration menu
    Copy the full SHA
    86b0b7f View commit details
    Browse the repository at this point in the history

  2. Update connection.rs

    @grahamc
    grahamc authored Dec 2, 2017
    Configuration menu
    Copy the full SHA
    506ce9b View commit details
    Browse the repository at this point in the history

  3. Update connection.rs

    @grahamc
    grahamc authored Dec 2, 2017
    Configuration menu
    Copy the full SHA
    5c30c53 View commit details
    Browse the repository at this point in the history

  4. Update connection.rs

    @grahamc
    grahamc authored Dec 2, 2017
    Configuration menu
    Copy the full SHA
    7aedd23 View commit details
    Browse the repository at this point in the history

Commits on Dec 5, 2017

  1. Update connection.rs

    @grahamc
    grahamc authored Dec 5, 2017
    Configuration menu
    Copy the full SHA
    d027bfd View commit details
    Browse the repository at this point in the history

  2. Update connection.rs

    @grahamc
    grahamc authored Dec 5, 2017
    Configuration menu
    Copy the full SHA
    8f40d62 View commit details
    Browse the repository at this point in the history

Commits on Dec 26, 2017

  1. Handle some kinds of io errors

    @grahamc
    grahamc committed Dec 26, 2017
    Configuration menu
    Copy the full SHA
    6911cae View commit details
    Browse the repository at this point in the history

  2. correct errors to traces

    @grahamc
    grahamc committed Dec 26, 2017
    Configuration menu
    Copy the full SHA
    07ff696 View commit details
    Browse the repository at this point in the history

Commits on Jan 13, 2018

  1. Send many writes in one go as possible to allow more write-heavy workers

    @grahamc
    grahamc committed Jan 13, 2018
    Configuration menu
    Copy the full SHA
    46c56b3 View commit details
    Browse the repository at this point in the history

Commits on Jan 25, 2018

  1. Handle errors via thee original Err, don't try to re-fetch because it… 

    … is likely gone already
    @grahamc
    grahamc committed Jan 25, 2018
    Configuration menu
    Copy the full SHA
    8325f89 View commit details
    Browse the repository at this point in the history

  2. amqp errors shouldn't bind ioerrors to protocol errors

    @grahamc
    grahamc committed Jan 25, 2018
    Configuration menu
    Copy the full SHA
    6fab84a View commit details
    Browse the repository at this point in the history

Commits on Jan 26, 2018

  1. basic_publish: warn when using immediate and mandatory options 

    The AMQP library cannot appropriate handle failures in either of these
cases. It is easy for a channel's SyncSender to become full of
NO_ROUTE messages due to mandatory delivery failing. This effectively
causes a deadlock of the client.
    @grahamc
    grahamc committed Jan 26, 2018
    Configuration menu
    Copy the full SHA
    9316088 View commit details
    Browse the repository at this point in the history

  2. Remove take_error

    @grahamc
    grahamc committed Jan 26, 2018
    Configuration menu
    Copy the full SHA
    24b38be View commit details
    Browse the repository at this point in the history

  3. Log frame payload on dropped frames from channel 0

    @grahamc
    grahamc committed Jan 26, 2018
    Configuration menu
    Copy the full SHA
    7dc5373 View commit details
    Browse the repository at this point in the history

  4. Properly handle full MPSC queues in the consumer

    @grahamc
    grahamc committed Jan 26, 2018
    Configuration menu
    Copy the full SHA
    452aee8 View commit details
    Browse the repository at this point in the history