{"push_id":1774626063,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"7a2862a933addface23586ef01ac555543a228c7","before":"e80f4c91d0a2854a339e419162fdcd1d916f7de0","commits":[{"sha":"7a2862a933addface23586ef01ac555543a228c7","author":{"name":"henrik.lundin","email":"8daf97c1c6fba932f6ab3a2c7a5c0f99fdb23bdd@webrtc.org"},"message":"Fix a bug in RtcEventLogSource\n\nA recent change (https://codereview.webrtc.org/2855143002/) introduced\na bug in RtcEventLogSource::NextPacket(). The rtp_packet_index_ must\nbe incremented when a valid packet is found and delivered. Otherwise,\nthe same packet will be delivered over and over again.\n\nThe recent change also altered the way that audio packets are sifted out. Now, the RTP header is always parsed before discarding any non-audio packets. This means that RtpHeaderParser::Parse is always called, also with video packets, which sometimes contain padding. When header-only dumps (such as RtcEventLogs) are created, the payload is stripped, and the payload length is equal to\nthe RTP header length. However, if the original packet was padded, the\nRTP header will carry information about this padding length, and the\nparser will check that the pyaload length is at least the header +\npadding. This is not the case for header-only dumps, and the parser will return an error. In this CL, we ignore that error when a header-only packet has padding length larger than 0.\n\nBUG=webrtc:7538\n\nReview-Url: https://codereview.webrtc.org/2912323003\nCr-Commit-Position: refs/heads/master@{#18385}","distinct":true,"url":"https://api.github.com/repos/pristineio/webrtc-mirror/commits/7a2862a933addface23586ef01ac555543a228c7"}]}
{"actor":{"display_login":"jenkins-pristine"}}