[GitHub] [kafka] mjsax commented on pull request #9634: KAFKA-10755: Should consider commit latency when computing next commit timestamp

2020-11-20 Thread GitBox 


mjsax commented on pull request #9634:
URL: https://github.com/apache/kafka/pull/9634#issuecomment-731499093


   Merged to `trunk` and cherry-picked to `2.6`. Will cherry pick to `2.7` 
after release is done.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [kafka] mjsax commented on pull request #9634: KAFKA-10755: Should consider commit latency when computing next commit timestamp

2020-11-21 Thread GitBox 


mjsax commented on pull request #9634:
URL: https://github.com/apache/kafka/pull/9634#issuecomment-731626196


   Jenkins build was green... Not sure how this happened.
   
   It seems, I did start the PR from a stale local `trunk` branch. But Jenkins 
build should have caught the issue. Not sure why?



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [kafka] mjsax commented on pull request #9634: KAFKA-10755: Should consider commit latency when computing next commit timestamp

2020-11-24 Thread GitBox 


mjsax commented on pull request #9634:
URL: https://github.com/apache/kafka/pull/9634#issuecomment-733178631


   Cherry-picked to `2.7` branch.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org