)]}'
{"nova/api/openstack/compute/contrib/admin_actions.py":[{"author":{"_account_id":4419,"name":"Matthew Sherborne","email":"msherborne+openstack@gmail.com","username":"msherborne+openstack"},"change_message_id":"c89fed9c355cfab42abae85dd68f96be772fccc6","unresolved":false,"context_lines":[{"line_number":283,"context_line":"            self.compute_api.live_migrate(context, instance, block_migration,"},{"line_number":284,"context_line":"                                          disk_over_commit, host)"},{"line_number":285,"context_line":"        except exception.ComputeServiceUnavailable as ex:"},{"line_number":286,"context_line":"            raise exc.HTTPBadRequest(explanation\u003dunicode(ex))"},{"line_number":287,"context_line":"        except Exception:"},{"line_number":288,"context_line":"            msg \u003d _(\"Live migration of instance %(id)s to host %(host)s\""},{"line_number":289,"context_line":"                    \" failed\") % locals()"}],"source_content_type":"text/x-python","patch_set":3,"id":"AAAAM3%2F%2FSaw%3D","line":286,"updated":"2013-01-30 06:09:09.000000000","message":"I think we should drop the \u0027unicode\u0027, and just go \u0027ex.message\u0027\n\nunicode on it\u0027s own assumes the string is in ASCII format and throws an exception if it has a non ASCII char in it.\n\nAs the actual encoding is defined in the transation\u0027s .po file, there\u0027s no way to turn that 8 bit string into a unicode string reliably. Best to just send it to the user in whatever encoding the translator decided to use, I think.\n\nExample of what happens when you pass it utf-8 (pretend the ? is a chinese char :)\n\n\u003e\u003e\u003e unicode(\u0027?\u0027)\nTraceback (most recent call last):\n  File \"\u003cstdin\u003e\", line 1, in \u003cmodule\u003e\nUnicodeDecodeError: \u0027ascii\u0027 codec can\u0027t decode byte 0xe7 in position 0: ordinal not in range(128)","commit_id":"4b4d0e1f2c41c02eed719b97985757f407438739"}],"nova/scheduler/manager.py":[{"author":{"_account_id":1970,"name":"Jacob Wen","email":"wenjianhn@gmail.com","username":"wenjianhn"},"change_message_id":"e4ed0cb6512ad8b1592b11bced9b393a9706b139","unresolved":false,"context_lines":[{"line_number":106,"context_line":"            with excutils.save_and_reraise_exception():"},{"line_number":107,"context_line":"                self._set_vm_state_and_notify(\u0027live_migration\u0027,"},{"line_number":108,"context_line":"                                             {\u0027vm_state\u0027: vm_states.ERROR},"},{"line_number":109,"context_line":"                                             context, ex, {})"},{"line_number":110,"context_line":""},{"line_number":111,"context_line":"    def run_instance(self, context, request_spec, admin_password,"},{"line_number":112,"context_line":"            injected_files, requested_networks, is_first_time,"}],"source_content_type":"text/x-python","patch_set":1,"id":"AAAAM3%2F%2Fmr4%3D","line":109,"updated":"2013-01-14 12:19:37.000000000","message":"The reason of instance vm_state is not updated to ERROR when ComputeServiceUnavailable before this patch is that empty request_spec is passed in set_vm_state_and_notify makes no db update. This is still a bug. I will fix this in another patch in order to make this patch smaller.","commit_id":"f0b01a49e49cb12ae71d736756431f159f7a8e1f"}]}