{"push_id":1041559451,"size":1,"distinct_size":1,"ref":"refs/heads/research/code-footprint","head":"be7c4bd692eeb9723b4eaf26cb8e69f1e9d137ee","before":"e9f4d1fc8531bc86f71115cdb9aea3b7a9d701bf","commits":[{"sha":"be7c4bd692eeb9723b4eaf26cb8e69f1e9d137ee","author":{"email":"8087404fbdd07c5fc5dabfc45455106612d1ab91@gmail.com","name":"Maxime Colmant"},"message":"feature(code-energy-analysis): create an app for producing power estimation at method level\n\nThe new app acts like a daemon for getting information about the function which has been at the origin of the interruption.\nA PowerAPI agent has to be attached to a program (which can be compiled with the -rdynamic option for now) for setting the interruption mode on it and getting information about the running function when the handler is triggered.\nThe agent then sends data to PowerAPI other Unix sockets for computing power estimation.","distinct":true,"url":"https://api.github.com/repos/Spirals-Team/powerapi/commits/be7c4bd692eeb9723b4eaf26cb8e69f1e9d137ee"}]}