)]}'
{"taskflow/flow.py":[{"author":{"_account_id":9648,"name":"Greg Hill","email":"greg.hill@rackspace.com","username":"jimbobhickville"},"change_message_id":"dc5ecaf17131ce96ac97d8f943b3cf768bf9429a","unresolved":false,"context_lines":[{"line_number":61,"context_line":"        # NOTE(akarpinska): if retry doesn\u0027t have a name, the name of its"},{"line_number":62,"context_line":"        # owner will be used instead (with a \u0027_retry\u0027 postfix)"},{"line_number":63,"context_line":"        if self._retry is not None and not self._retry.name:"},{"line_number":64,"context_line":"            if not self._name:"},{"line_number":65,"context_line":"                raise ValueError(\"Attaching a unnamed retry controller \u0027%s\u0027\""},{"line_number":66,"context_line":"                                 \" to a unnamed flow is not supported\" % retry)"},{"line_number":67,"context_line":"            self._retry.name \u003d self.name + \"_retry\""}],"source_content_type":"text/x-python","patch_set":2,"id":"fa69d971_dc3d11de","line":64,"updated":"2016-01-05 15:04:06.000000000","message":"If we can\u0027t automatically give the retry atom a name, I\u0027m not sure how useful making flow name optional is. \u0027name is optional unless you have a retry\u0027 is kind of confusing to users. I\u0027d vote that we either generate a unique name for the retry atom if the flow isn\u0027t named or just abandon the idea altogether.","commit_id":"0fd1144db2e8ff60f8868424e8dd6e8944f1a7a0"}]}