Jasper Paul Sikorra

Using the :skip_parse option with JSON::Hash values produces Pipeline::Stop

1

Using the option `:skip_parse` with `values` will set `Representable::Pipeline::Stop` on the represented object. I expected it to be `nil`. ```ruby class SomeRepresenter < Grape::Roar::Decorator include Roar::JSON include Roar::Coercion include Representable::JSON::Hash...

See https://github.com/murbanski/omniauth-microsoft-office365/issues/22 See https://github.com/omniauth/omniauth/commit/c606a00798a7f516c37c67a708864f9a3eb9f796#diff-c2f37e7010d83348d856f2e436efbfc2a93e396b200d1f6f8821ced735463ce8R480 and https://github.com/omniauth/omniauth/commit/c606a00798a7f516c37c67a708864f9a3eb9f796#diff-c2f37e7010d83348d856f2e436efbfc2a93e396b200d1f6f8821ced735463ce8R437 for the commit that added script_name to the callback_path.

In https://github.com/omniauth/omniauth/pull/903 `callback_path` was changed to include `script_name`, so this gem will not work with Omniauth 2.0. Different gems already fixed this (see https://github.com/simi/omniauth-facebook/pull/380).

OpenSSL::SSL::SSLErrorWaitReadable with TLS 1.3

8

Starting in April we started seeing lots of "read would block" and OpenSSL::SSL::SSLErrorWaitReadable errors in our Sentry instance. The errors occur only with TLS 1.3 and not with TLS 1.2....

If multiple certificates with the same subjectdn are added to the store and used to verify, this can still fail based on the order they were placed in the store....