GitHub PushEvent at 2014-09-29 10:03:18
Repository: core
Actor: kacfengine
Payload: {"shas":[["6b544dbae2baa0a305ecac3c0fe8d24c641a9878","1df6cae165d9bb405b07b43648cf9ecfe9cfddf8@cfengine.com","Improved Log()ging and fixed a leak in evalfunction's JSON wrappers.\n\nSuccessful parse yielding a non-container was conflated with failed\nparsing; separate the two.  In the process, fix the leak of the json\nobject when it's not a container; and report *what* failed when we\ndidn't even get that.  Use JsonParseFile() in the one place that we're\njust duplicating it's workings.","Edward Welbourne",true],["1812325c7e0fb8788056b7963ce01c56e6662543","1df6cae165d9bb405b07b43648cf9ecfe9cfddf8@cfengine.com","Eliminate pointless intermediary in JsonParseFile()\n\nWe're going to write to the pointer we were passed in any case, so we\nmay as well pass that into the parser for it to write to, instead of\nhaving our own local variable to passdown and then copy to the pointer\nwe received.","Edward Welbourne",true],["95f8d71a59a064ad22535529da44a6ad958206f7","1df6cae165d9bb405b07b43648cf9ecfe9cfddf8@cfengine.com","redmine6549: Tolerate unrecognised escape sequences.\n\nWe have no way to represent \\u{hex digit} escapes for Unicode, which\nare perfectly valid JSON; so we need to tolerate these in some form\nrather than choking on them.  Given that the only sane way to do so is\nto preserve them verbatim, we may as well do the same for any other\nunrecognised escapes.  This eliminates the need for an error code to\nrepresent unrecognised escape.\n\nLog() a warning when handling an escape verbatim, though; which, in\nturn, requires a #include <logging.h>","Edward Welbourne",true],["a9188230c52006c16180ab35a380cffa73bec964","1df6cae165d9bb405b07b43648cf9ecfe9cfddf8@cfengine.com","Add acceptance test for unicode escapes in JSON.","Edward Welbourne",true],["42ce547ecb73a1bbd0cb5f926a18977f59272185","505e66ae45028a0596c853559221f0b72c1cee21@cfengine.com","Merge pull request #1995 from ediosyncratic/json-parsing-fix\n\nRedMine 6549: deal with some problems with parsing JSON","Kristian Amlie",true]],"size":5,"ref":"refs/heads/master","head":"42ce547ecb73a1bbd0cb5f926a18977f59272185"}