{"push_id":821748751,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"821b54921a3cba5d853b531d4b03527c01bfc9b4","before":"b43773192c6a9b4f7ce781028d42ed3efa4097cb","commits":[{"sha":"821b54921a3cba5d853b531d4b03527c01bfc9b4","author":{"email":"efbd50075b4270ebb1b541c4fc9591635eb6130d@gmail.com","name":"mpl"},"message":"mime/multipart: fix peekBufferSeparatorIndex edge case\n\nThe case fixed by this change happens when, in func (pr partReader)\nRead, the Peek happens to read so that peek looks like:\n\n  \"somedata\\r\\n--Boundary\\r\"\n\npeekBufferSeparatorIndex was returning (-1, false) because it didn't\nfind the trailing '\\n'.\n\nThis was wrong because:\n\n1) It didn't match the documentation: as \"\\r\\n--Boundary\" was found, it\nshould return the index of that pattern, not -1.\n\n2) It lead to an nCopy cut such as:\n  \"somedata\\r| |\\n--Boundary\\r\" instead of \"somedata| |\\r\\n--Boundary\\r\"\nwhich made the subsequent Read miss the boundary, and eventually end\nwith a \"return 0, io.ErrUnexpectedEOF\" case, as reported in:\n\nhttps://github.com/camlistore/camlistore/issues/642\n\nChange-Id: I1ba78a741bc0c7719e160add9cca932d10f8a615\nReviewed-on: https://go-review.googlesource.com/15269\nReviewed-by: Brad Fitzpatrick <bradfitz@golang.org>\nRun-TryBot: Brad Fitzpatrick <bradfitz@golang.org>","distinct":true,"url":"https://api.github.com/repos/golang/go/commits/821b54921a3cba5d853b531d4b03527c01bfc9b4"}]}