{"push_id":1445089202,"size":1,"distinct_size":1,"ref":"refs/heads/fix-parser-issue-with-more-data","head":"509409635c23bd0c647412a6e0e290689de1ae14","before":"25c1b114d03e4c4587e9ee8683922182f97a1197","commits":[{"sha":"509409635c23bd0c647412a6e0e290689de1ae14","author":{"name":"Lars Hesel Christensen","email":"7f698333860e9f21dcc513102ebee3bcaf8d683e@larshesel.dk"},"message":"Fix another issue in the parser logic\n\nWhen fixing the last parser issue, we inadvertendly changed the logic so\nparse/4 would be returning `packet_exceeds_max_size` when `MaxSize=0`\nand `byte_size(Data) < DataSize` which of course makes no sense.\n\nThis commits makes sure we handle all six cases:\n\n- no max, enough data -> parse\n- no max, not enough data -> more\n- max - enough data - max exceeded -> error max exceeded\n- max - enough data - max not exceeded -> parse\n- max - not enough data - max exceeded -> error max exceeded\n- max - not enough data - max not exceeded -> more","distinct":true,"url":"https://api.github.com/repos/larshesel/vernemq/commits/509409635c23bd0c647412a6e0e290689de1ae14"}]}
{"actor":{"display_login":"larshesel"}}