{"push_id":617327998,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"f367b695f1fa87c040466785092a001127904107","before":"e7ef356de5e6d6f931478e92cc000480d8284974","commits":[{"sha":"5874981d1a6b777b828229a6d7f86a522d70549a","author":{"email":"e281c252d198e5ffcb2c82d556799e5f60def33d@videolabs.io","name":"Steve Lhomme"},"message":"deinterlace: fix MSVC compilation\n\nSigned-off-by: Hugo Beauzée-Luyssen <hugo@beauzee.fr>","distinct":true,"url":"https://api.github.com/repos/videolan/vlc/commits/5874981d1a6b777b828229a6d7f86a522d70549a"},{"sha":"f367b695f1fa87c040466785092a001127904107","author":{"email":"d4c5dd7b5e122ce17d012dffdd83773a826bdf11@gunderson.no","name":"Steinar H. Gunderson"},"message":"Fix Metacube header handling with multiple header blocks.\n\nSome muxes, e.g. MP4, will send multiple header blocks. These are\nmerged by the HTTP server to a single header which is sent out to\nthe beginning of each client. However, they are _also_ sent out\ndirectly on the wire to any client that connected before the first\nblock. In this case, we would send two separate Metacube header\nblocks, which would have Cubemap (correctly) discard the first and\nset only the second as header.\n\nThis would make us send only part of the MP4 header when sending\nthrough Cubemap, if Cubemap connected before the first non-header\nblock, which would in turn confuse Chrome on Android (although not\nChrome on e.g. Linux). As Cubemap is pretty aggressive about\nreconnecting (trying every 200 ms), this could easily happen in practice.\n\nSigned-off-by: Jean-Baptiste Kempf <jb@videolan.org>","distinct":true,"url":"https://api.github.com/repos/videolan/vlc/commits/f367b695f1fa87c040466785092a001127904107"}]}