{"push_id":1370090908,"size":1,"distinct_size":1,"ref":"refs/heads/truncate-twrite-msize","head":"7725b53249beb422f91eb13c2be5136956b93e3a","before":"9c7316bf1f66c606fee277e573e643ae24320bda","commits":[{"sha":"7725b53249beb422f91eb13c2be5136956b93e3a","author":{"name":"Stephen J Day","email":"f612758db3805c4abe0d56243c03a33f3294af3f@docker.com"},"message":"channel: truncate twrite messages based on msize\n\nWhile there are a few problems around handling of msize, the easiest to\naddress and, arguably, the most problematic is that of Twrite. We now\ntruncate Twrite.Data to the correct length if it will overflow the msize\nlimit negotiated on the session. ErrShortWrite is returned by the\n`Session.Write` method if written data is truncated.\n\nOther problems with Twrite/Rread are documented in TODOs here, along\nwith possible solutions.\n\nSigned-off-by: Stephen J Day <stephen.day@docker.com>","distinct":true,"url":"https://api.github.com/repos/stevvooe/go-p9p/commits/7725b53249beb422f91eb13c2be5136956b93e3a"}]}
{"actor":{"display_login":"stevvooe"}}