{"push_id":826821408,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"51adc9d8894878642fca75f269695267edb01693","before":"af25e3cc93ec5c6d5fce8e0b9631a76423134a02","commits":[{"sha":"21c6da6764c0cd015e9f3c5eecba36e297187deb","author":{"email":"4bedcc74ac66610c2f47a8e5724855062d99c774@digisoft.tv","name":"Stavros Vagionitis"},"message":"souphttpsrc: Make non-inclusive segment boundaries inclusive\n\nThe problem is that the filesrc and souphttpsrc are behaving\ndifferently regarding the calculation of the segment boundaries. The\nfilesrc is using a non-inclusive boundaries, while the souphttpsrc\nuses inclusive. Currently the hlsdemux calculates the boundaries as\ninclusive, so for this reason there is no problem with the souphttpsrc,\nbut there is an issue in the filesrc.\n\nThe GstSegment is non-inclusive, so the proposed solution is to use\nnon-inclusive boundaries in the hlsdemux in order to be consistent.\nMake the change in the hlsdemux, will break the souphttpsrc, which\nwill expect inclusive boundaries, but the hlsdemux will offer\nnon-inclusive. This change makes sure that the non-inclusive\nboundaries are converted to inclusive.\n\nhttps://bugzilla.gnome.org/show_bug.cgi?id=748316","distinct":true,"url":"https://api.github.com/repos/gstreamer-mirror/gst-plugins-good/commits/21c6da6764c0cd015e9f3c5eecba36e297187deb"},{"sha":"51adc9d8894878642fca75f269695267edb01693","author":{"email":"db043b2055cb3a47b2eb0b5aebf4e114a8c24a5a@centricular.com","name":"Sebastian Dröge"},"message":"souphttpsrc: EOS immediately if we have an empty seek segment\n\nhttps://bugzilla.gnome.org/show_bug.cgi?id=748316","distinct":true,"url":"https://api.github.com/repos/gstreamer-mirror/gst-plugins-good/commits/51adc9d8894878642fca75f269695267edb01693"}]}