{"push_id":821024098,"size":2,"distinct_size":2,"ref":"refs/heads/switch_to_our_format","head":"ec004153d40a61e10097e01debabb76bf1cdf444","before":"1043097480f1383f5753602a3ddf7b6a48a1291e","commits":[{"sha":"a24b2f2d8fa2cb7c070dfd2000f2f548f06989cf","author":{"email":"52585e8ec27a51541558101da8c5ed713d6a4cbe@eecs.berkeley.edu","name":"K. Shankari"},"message":"Minor logging changes\n\n- Convert print statements to logging so that they go into their proper place with a timestamp\n- Comment out extra verbose statement that doesn't actually give us a lot of additional information","distinct":true,"url":"https://api.github.com/repos/shankari/e-mission-server/commits/a24b2f2d8fa2cb7c070dfd2000f2f548f06989cf"},{"sha":"ec004153d40a61e10097e01debabb76bf1cdf444","author":{"email":"52585e8ec27a51541558101da8c5ed713d6a4cbe@eecs.berkeley.edu","name":"K. Shankari"},"message":"Add support for storing the last processed timestamp in the database\n\nBefore this, we assumed that all data that was before the last run time had\nbeen processed. But when data is collected on the client, it is possible for it\nto have been collected before the last run but not yet transmitted to the\nserver. So when it does get to the server, it will be ignored.\n\nWith this change, we introduce the concept of a last_processed timestamp that\nis distinct from the last run, update it for stages that use client provided\nvalues for queries, and use it to determine the points processed in the next\nrun.","distinct":true,"url":"https://api.github.com/repos/shankari/e-mission-server/commits/ec004153d40a61e10097e01debabb76bf1cdf444"}]}