kafka git commit: KAFKA-4861; GroupMetadataManager record is rejected if broker configured with LogAppendTime

Repository: kafka Updated Branches: refs/heads/0.10.2 3445ed0ba -> beb0d5700 KAFKA-4861; GroupMetadataManager record is rejected if broker configured with LogAppendTime The record should be created with CreateTime (like in the producer). The conversion to LogAppendTime happens automatically

kafka git commit: KAFKA-4861; GroupMetadataManager record is rejected if broker configured with LogAppendTime

Repository: kafka Updated Branches: refs/heads/trunk dbcbd7920 -> 7565dcd8b KAFKA-4861; GroupMetadataManager record is rejected if broker configured with LogAppendTime The record should be created with CreateTime (like in the producer). The conversion to LogAppendTime happens automatically (

kafka git commit: KAFKA-4467: Run tests on travis-ci using docker

Repository: kafka Updated Branches: refs/heads/trunk 65650ba4d -> dbcbd7920 KAFKA-4467: Run tests on travis-ci using docker ijuma ewencp cmccabe harshach Please review. Here is a sample run: https://travis-ci.org/raghavgautam/kafka/builds/191714520 In this run 214 tests were run and 144 tests

kafka git commit: MINOR: Introduce NetworkClient.hasInFlightRequests

Repository: kafka Updated Branches: refs/heads/trunk 294018a57 -> 65650ba4d MINOR: Introduce NetworkClient.hasInFlightRequests It’s a minor optimisation, but simple enough. Author: Ismael Juma Reviewers: Apurva Mehta , Jason Gustafson Closes #2658 from ijuma/has-in-flight-requests Pr