)]}'
{"examples/pki/cms/auth_token_unscoped.json":[{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"da06d46420d47dd2dcc604d9d3d7e43fb0db90b1","unresolved":false,"context_lines":[{"line_number":1,"context_line":"{\"access\": {\"token\": {\"expires\": \"2012-08-17T15:35:34Z\", \"id\": \"01e032c996ef4406b144335915a41e79\"}, \"serviceCatalog\": {}, \"user\": {\"username\": \"user_name1\", \"roles_links\": [], \"id\": \"c9c89e3be3ee453fbf00c7966f6d3fbd\", \"roles\": [{\"name\": \"role1\"},{\"name\": \"role2\"}], \"name\": \"user_name1\"}}}"}],"source_content_type":"application/json","patch_set":2,"id":"AAAATn%2F%2FXmI%3D","line":1,"updated":"2013-11-08 03:36:11.000000000","message":"should there be a space after the comma between the 2 roles?\n\n\"role1\"},{\"name\"\n\n\n\"role1\"}, {\"name\"","commit_id":"3f179e439107b6bde08361664bfa225e7726afd0"},{"author":{"_account_id":9259,"name":"Rick Hull","email":"rick@cloudscaling.com","username":"rickhull"},"change_message_id":"0d16c3dfdbf724d6d3d88773ae8e5d9b96f69cce","unresolved":false,"context_lines":[{"line_number":1,"context_line":"{\"access\": {\"token\": {\"expires\": \"2012-08-17T15:35:34Z\", \"id\": \"01e032c996ef4406b144335915a41e79\"}, \"serviceCatalog\": {}, \"user\": {\"username\": \"user_name1\", \"roles_links\": [], \"id\": \"c9c89e3be3ee453fbf00c7966f6d3fbd\", \"roles\": [{\"name\": \"role1\"},{\"name\": \"role2\"}], \"name\": \"user_name1\"}}}"}],"source_content_type":"application/json","patch_set":2,"id":"AAAATn%2F%2FXXs%3D","line":1,"in_reply_to":"AAAATn%2F%2FXmI%3D","updated":"2013-11-08 05:57:10.000000000","message":"that would match the existing style -- it\u0027s not a parse issue, though.  It looks pretty clear that someone copy/pasted reasonable-looking but invalid JSON inside the \"roles\" collection, which presumably was generated empty by some tool.","commit_id":"3f179e439107b6bde08361664bfa225e7726afd0"}]}
