{"push_id":945293958,"size":9,"distinct_size":9,"ref":"refs/heads/4.0","head":"5466f68f7847ff299fce8f817faa40f9295e2147","before":"091618221af946049ad0171034ea133a71c679d3","commits":[{"sha":"95b1705711b08b0e49a6791d923fb5c285d2cd61","author":{"email":"330e4303411e1fbd4ff825c4416851d277ea7a5f@apple.com","name":"Norman Maurer"},"message":"[#4694] Ensure native transport can also be compiled on 32bit systems.\n\nMotivation:\n\nWe should also be able to compile the native transport on 32bit systems.\n\nModifications:\n\nAdd cast to intptr_t for pointers\n\nResult:\n\nIt's possible now to also compile on 32bit.","distinct":true,"url":"https://api.github.com/repos/zzcclp/netty/commits/95b1705711b08b0e49a6791d923fb5c285d2cd61"},{"sha":"53323530c1b47e225c28fc4e3a4a4f9de1b7a0e3","author":{"email":"a8c456a6b54fc41d6e961143bac21b6e0910a8a8@apple.com","name":"Scott Mitchell"},"message":"Native Transport Netty Class Package Prefix\n\nMotivation:\ntransport-native-epoll finds java classes from JNI using fully qualified class names. If a shaded version of Netty is used then these lookups will fail.\n\nModifications:\n- Allow a prefix to be appended to Netty class names in JNI code.\n\nResult:\nJNI code can be used with shaded version of Netty.","distinct":true,"url":"https://api.github.com/repos/zzcclp/netty/commits/53323530c1b47e225c28fc4e3a4a4f9de1b7a0e3"},{"sha":"8bfbb359796e415765d432af1d41e6e935805c10","author":{"email":"330e4303411e1fbd4ff825c4416851d277ea7a5f@apple.com","name":"Norman Maurer"},"message":"Ensure connectPromise is not notified before fireChannelActive() is called.\n\nMotivation:\n\nOur contract in Channels is that the promise should always be notified before the actual callbacks of the ChannelInboundHandler are called. This was not done in the LocalChannel and so the behavior was different to other Channel implementations.\n\nModifications:\n\n- First complete the ChannelPromise then call fireChannelActive()\n- Guard against NPE when doClose() was called before the task was executed.\n\nResult:\n\nConsistent behavior between LocalChannel and other Channel implementations.","distinct":true,"url":"https://api.github.com/repos/zzcclp/netty/commits/8bfbb359796e415765d432af1d41e6e935805c10"},{"sha":"d7d64137e02c50811af3bc58dfb7d98a38ec9566","author":{"email":"330e4303411e1fbd4ff825c4416851d277ea7a5f@apple.com","name":"Norman Maurer"},"message":"Let CombinedChannelDuplexHandler correctly handle exceptionCaught. Related to [#4528]\n\nMotivation:\n\nChannelInboundHandler and ChannelOutboundHandler both can implement exceptionCaught(...) method and so we need to dispatch to both of them.\n\nModifications:\n\n- Correctly first dispatch exceptionCaught to the ChannelInboundHandler but also make sure the next handler it will be dispatched to will be the ChannelOutboundHandler\n- Add removeInboundHandler() and removeOutboundHandler() which allows to remove one of the combined handlers\n\nResult:\n\nCorrectly handle events","distinct":true,"url":"https://api.github.com/repos/zzcclp/netty/commits/d7d64137e02c50811af3bc58dfb7d98a38ec9566"},{"sha":"18765a3bf7bf85b541897bc9b3dd8e0c57482614","author":{"email":"330e4303411e1fbd4ff825c4416851d277ea7a5f@apple.com","name":"Norman Maurer"},"message":"[#4017] Implement proper resource leak detection for CompositeByteBuf\n\nMotivation:\n\nCompositeByteBuf only implemented simple resource leak detection and how it was implemented was completly different to the way it was for ByteBuf. The other problem was that slice(), duplicate() and others would not return a resource leak enabled buffer.\n\nModifications:\n\n- Proper implementation for all level of resource leak detection for CompositeByteBuf\n\nResult:\n\nProper resource leak detection for CompositeByteBuf.","distinct":true,"url":"https://api.github.com/repos/zzcclp/netty/commits/18765a3bf7bf85b541897bc9b3dd8e0c57482614"},{"sha":"ef2cf4625d78d35a956ec8f18d80fb3c2e63cbd7","author":{"email":"330e4303411e1fbd4ff825c4416851d277ea7a5f@apple.com","name":"Norman Maurer"},"message":"[#4725] Ensure correct cause of handshake error is included in the SSLHandshakeException when using OpenSslEngine.\n\nMotivation:\n\nWe need to ensure we add the correct handshake error to the SSLHandshakeException before throwing it when failing the\nhandshake.\n\nModifications:\n\nUse the correct error string when creating the SSLHandshakeException.\n\nResult:\n\nCorrect SSLHandshakeException message included.","distinct":true,"url":"https://api.github.com/repos/zzcclp/netty/commits/ef2cf4625d78d35a956ec8f18d80fb3c2e63cbd7"},{"sha":"92896bd7bde7dc9d05095ae3e1a1b3ff7a0e796d","author":{"email":"a8c456a6b54fc41d6e961143bac21b6e0910a8a8@apple.com","name":"Scott Mitchell"},"message":"PlatformDependent static initialization ExceptionInInitializerError\n\nMotivation:\nPlatformDependent allows some exceptions to escape during static initialization. If an exception escapes it will be translated into a java.lang.ExceptionInInitializerError and render the application unable to run.\n\nModifications:\n- Make sure to catch Throwable during static initialization.\n\nResult:\nPlatformDependent static initialization doesn't result in java.lang.ExceptionInInitializerError.","distinct":true,"url":"https://api.github.com/repos/zzcclp/netty/commits/92896bd7bde7dc9d05095ae3e1a1b3ff7a0e796d"},{"sha":"ae6c74d51aa623719460bddea40181783875b515","author":{"email":"330e4303411e1fbd4ff825c4416851d277ea7a5f@apple.com","name":"Norman Maurer"},"message":"Ensure we flush out all pending data on SslException. Related to [#3900]\n\nMotivation:\n\nWe need to ensure we flush out all pending data when an SslException accours so the remote peer receives all alerts.\n\nModifications:\n\nEnsure we call ctx.flush() when needed.\n\nResult:\n\nCorrectly receive alerts in all cases on the remote peer.","distinct":true,"url":"https://api.github.com/repos/zzcclp/netty/commits/ae6c74d51aa623719460bddea40181783875b515"},{"sha":"5466f68f7847ff299fce8f817faa40f9295e2147","author":{"email":"28ee1748f767fb3d6cbcefc6a52697fa889080fa@gmail.com","name":"Xiaoyan Lin"},"message":"Change 64 to 63 in Snappy.decodeLiteral\n\nMotivation:\n\nAccording to https://github.com/google/snappy/blob/master/format_description.txt#L55 , Snappy.decodeLiteral should handle the cases of 60, 61, 62 and 63. However right now it processes 64 instead of 63. I believe it's a typo since `tag >> 2 & 0x3F` must be less than 64.\n\nModifications:\n\nUse the correct value 63.\n\nResult:\n\nSnappy.decodeLiteral handles the correct case.","distinct":true,"url":"https://api.github.com/repos/zzcclp/netty/commits/5466f68f7847ff299fce8f817faa40f9295e2147"}]}