)]}'
{"oslo_service/service.py":[{"author":{"_account_id":14358,"name":"Marian Horban","email":"m.horban@gmail.com","username":"mhorban"},"change_message_id":"2754e413e6add18fc02eb5d6fcd183699e9d49b6","unresolved":false,"context_lines":[{"line_number":444,"context_line":""},{"line_number":445,"context_line":"            os._exit(status)"},{"line_number":446,"context_line":""},{"line_number":447,"context_line":"        LOG.debug(\u0027Started child %d\u0027, pid)"},{"line_number":448,"context_line":""},{"line_number":449,"context_line":"        wrap.children.add(pid)"},{"line_number":450,"context_line":"        self.children[pid] \u003d wrap"}],"source_content_type":"text/x-python","patch_set":1,"id":"da85f559_fd1b3c71","line":447,"updated":"2015-11-11 10:18:20.000000000","message":"I believe this event is important and should have INFO log level. Maybe message must be changed to something like: \"Worker was respawned successfully\"","commit_id":"8654650f0872dfcf4a71bbc45ebe11699276c9dc"},{"author":{"_account_id":7293,"name":"Elena Ezhova","email":"ezhovaelena19@gmail.com","username":"elena"},"change_message_id":"525da885c8503dca0d3d54251e835fd263a9c91b","unresolved":false,"context_lines":[{"line_number":444,"context_line":""},{"line_number":445,"context_line":"            os._exit(status)"},{"line_number":446,"context_line":""},{"line_number":447,"context_line":"        LOG.debug(\u0027Started child %d\u0027, pid)"},{"line_number":448,"context_line":""},{"line_number":449,"context_line":"        wrap.children.add(pid)"},{"line_number":450,"context_line":"        self.children[pid] \u003d wrap"}],"source_content_type":"text/x-python","patch_set":1,"id":"da85f559_bdbcd4dc","line":447,"in_reply_to":"da85f559_fd1b3c71","updated":"2015-11-11 10:24:40.000000000","message":"I agree with Marian, it can be important for an operator to know that all workers we spawned successfully. But I\u0027d also like to add that knowing process\u0027s pid is important too.","commit_id":"8654650f0872dfcf4a71bbc45ebe11699276c9dc"}]}