{"push_id":2885055657,"size":4,"distinct_size":4,"ref":"refs/heads/trunk","head":"c5ef614bbf133e18bd207e22f2697a2d1d3e8e4e","before":"3a8ab3258f8b461239bc7c0202f81c611745eee9","commits":[{"sha":"607dea234f30a0c40d5a48f518a51372e02fa0a0","author":{"name":"John Roesler","email":"884ff5c4006c6f627a23dfdf6dcce23badd4698e@users.noreply.github.com"},"message":"MINOR: log and fail on missing task in Streams (#5655)\n\nMatthias J. Sax <mjsax@apache.org>, Guozhang Wang <wangguoz@gmail.com>","distinct":true,"url":"https://api.github.com/repos/huxihx/kafka/commits/607dea234f30a0c40d5a48f518a51372e02fa0a0"},{"sha":"b21c66f9484a47f549cdfbdf286158fb2d85ee78","author":{"name":"Manikumar Reddy","email":"5c5b03b4d6e1a3a45d39ad15b70eab568fe0a48b@gmail.com"},"message":"KAFKA-5690; Add support to list ACLs for a given principal (KIP-357)\n\nAuthor: Manikumar Reddy <manikumar.reddy@gmail.com>\n\nReviewers: Dong Lin <lindong28@gmail.com>\n\nCloses #5633 from omkreddy/KAFKA-5690-LIST-PER-PRICIPAL","distinct":true,"url":"https://api.github.com/repos/huxihx/kafka/commits/b21c66f9484a47f549cdfbdf286158fb2d85ee78"},{"sha":"5e72f66ab5c6220098ebbd20957a05a1ed657ab7","author":{"name":"Rajini Sivaram","email":"2e743c5cf650e12d7db950775eab7636545b5b8c@googlemail.com"},"message":"MINOR: Increase timeout in log4j system test to avoid transient failures (#5658)\n\nReviewers: Ismael Juma <ismael@juma.me.uk>","distinct":true,"url":"https://api.github.com/repos/huxihx/kafka/commits/5e72f66ab5c6220098ebbd20957a05a1ed657ab7"},{"sha":"c5ef614bbf133e18bd207e22f2697a2d1d3e8e4e","author":{"name":"Jason Gustafson","email":"68c46a606457643eab92053c1c05574abb26f861@confluent.io"},"message":"KAFKA-7414; Out of range errors should never be fatal for follower (#5654)\n\nThis patch fixes the inconsistent handling of out of range errors in the replica fetcher. Previously we would raise a fatal error if the follower's offset is ahead of the leader's and unclean leader election is not enabled. The behavior was inconsistent depending on the message format. With KIP-101/KIP-279 and the new message format, upon becoming a follower, the replica would use leader epoch information to reconcile the end of the log with the leader and simply truncate. Additionally, with the old format, the check is not really bulletproof for detecting data loss since the unclean leader's end offset might have already caught up to the follower's offset at the time of its initial fetch or when it queries for the current log end offset.\r\n\r\nWith this patch, we simply skip the unclean leader election check and allow the needed truncation to occur. When the truncation offset is below the high watermark, a warning will be logged. This makes the behavior consistent for all message formats and removes a scenario in which an error on one partition can bring the broker down.\r\n\r\nReviewers: Ismael Juma <ismael@juma.me.uk>, Jun Rao <junrao@gmail.com>","distinct":true,"url":"https://api.github.com/repos/huxihx/kafka/commits/c5ef614bbf133e18bd207e22f2697a2d1d3e8e4e"}]}
{"actor":{"display_login":"huxihx"}}