{"push_id":835176129,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"b5e62d5343488fa0e3526da769ea41b5ffc71ea3","before":"d53e802a0e134c1078be83f6cc72fec5ed69ad2e","commits":[{"sha":"b5e62d5343488fa0e3526da769ea41b5ffc71ea3","author":{"email":"2af29c404bc0109703564710c1b1124ed47197c2@frantic.com","name":"Jussi Kinnula"},"message":"Fix socket leak: Replace AnyEvent::HTTP::LWP::UserAgent with LWP::UserAgent\n\nThe reason to replace AnyEvent and AnyEvent::HTTP::LWP::UserAgent based\nrequests with LWP::UserAgent, is because of stability. It seems that at least\non certain Linux systems AnyEvent::HTTP::LWP::UserAgent starts to leak\nsockets. The socket leak will lead, that all the responses will start to fail.\n\nThe failure error message is \"Could not fetch access token: No such device\nor address at /app/local/lib/perl5/Facebook/Graph/AccessToken/Response.pm\nline 24.\" - which doesn't tell that much, but is related that the request did\nnever leave, because opening a socket failed.\n\nIt would be nice to fix AnyEvent::HTTP::LWP::UserAgent in general for the\nactual socket leak problem, but as the Facebook::Graph module is a dependency\nfor quite many business applications - it's imperative to use a stable HTTP\nclient. And as the Facebook::Graph module does not actually do anything\nasynchronously, it's not required to use an async HTTP client - at least for\nnow.","distinct":true,"url":"https://api.github.com/repos/jussikinnula/Facebook-Graph/commits/b5e62d5343488fa0e3526da769ea41b5ffc71ea3"}]}