commit | 6ce96b8349678189c32dcaf6954da129fe093ef6 | [log] [tgz] |
---|---|---|
author | Lari Hotari <lhotari@users.noreply.github.com> | Fri May 07 19:38:50 2021 +0300 |
committer | GitHub <noreply@github.com> | Fri May 07 09:38:50 2021 -0700 |
tree | 9355b05f82d58ee4b7f7ce0af71e3238c8985cf0 | |
parent | b606da7bc8dd1c6c8f610d5acf1403d798b6dcf1 [diff] |
[SECURITY] Upgrade Netty to 4.1.63.Final ### Motivation - addresses several CVEs ### Changes - Upgrade Netty to 4.1.63.Final - Upgrade netty-tcnative-boringssl-static to 2.0.36.Final - adapt API deprecation in PooledByteBufAllocator API Reviewers: Lari Hotari <None>, Andrey Yegorov <None>, Enrico Olivelli <eolivelli@gmail.com>, Matteo Merli <mmerli@apache.org> This closes #2696 from lhotari/lh-upgrade-Netty-4.1.63.Final and squashes the following commits: 6003a374d [Lari Hotari] Experiment: exclude TLSv1.3 from testing fcbd707a6 [Lari Hotari] Handle TLS connection problems when TLSv1.3 is used 86788ef35 [Lari Hotari] [Security] Upgrade Netty to 4.1.63.Final b606da7bc [Lari Hotari] Upgrade Lombok to 1.18.20 0f22d238c [Andrey Yegorov] fix: Bookkeeper client throttling logic is based upon entryId instead of ledgerId e5e76667b [YANGLiiN] [DOC] fix the no striping occurs condition to Qw=E
Apache BookKeeper is a scalable, fault tolerant and low latency storage service optimized for append-only workloads.
It is suitable for being used in following scenarios:
Please visit the Documentation from the project website for more information.
For filing bugs, suggesting improvements, or requesting new features, help us out by opening a Github issue or opening an Apache jira.
Subscribe or mail the user@bookkeeper.apache.org list - Ask questions, find answers, and also help other users.
Subscribe or mail the dev@bookkeeper.apache.org list - Join development discussions, propose new ideas and connect with contributors.
Join us on Slack - This is the most immediate way to connect with Apache BookKeeper committers and contributors.
We feel that a welcoming open community is important and welcome contributions.
See Developer Setup to get your local environment setup.
Take a look at our open issues: JIRA Issues Github Issues.
Review our coding style and follow our pull requests to learn about our conventions.
Make your changes according to our contribution guide.