)]}'
{"zuul/ansible/base/library/command.py":[{"author":{"_account_id":7118,"name":"Ian Wienand","email":"iwienand@redhat.com","username":"iwienand"},"change_message_id":"570f88280300210b5b275e58d05c3d81f6e8b699","unresolved":false,"context_lines":[{"line_number":429,"context_line":"                data \u003d to_bytes(data)"},{"line_number":430,"context_line":"            cmd.stdin.write(data)"},{"line_number":431,"context_line":"            cmd.stdin.close()"},{"line_number":432,"context_line":""},{"line_number":433,"context_line":"        # while True:"},{"line_number":434,"context_line":"        #     rfds, wfds, efds \u003d select.select(rpipes, [], rpipes, 1)"},{"line_number":435,"context_line":"        #     stdout +\u003d self._read_from_pipes(rpipes, rfds, cmd.stdout)"}],"source_content_type":"text/x-python","patch_set":2,"id":"9f560f44_a644251a","line":432,"updated":"2020-09-28 02:05:30.000000000","message":"Ok, some archaeology.  \n\nThis original idea seems to have been added by Iae4769f923ecf74462e1fe43168ea93ff1c61d6e which copied in the ansible code at or around [1].  It seems this re-wrote the output tracking, but didn\u0027t really ever take notice of the \"data\" argument.  There was no discussion in the change about this but it seems no particular reason why it was left out.\n\nThen this commented out code was added by I63f72b45ecb9533eac5ba9eb0eef426beec905e3 with the Ansible 2.4 update.  again no particular reference to why writing the data to stdin was not done.\n\nErgo my conclusion is probably that this was overlooked in the original change, and then subsequent changes have just maintained the status quo without any particular reason.  \n\n[1] https://github.com/ansible/ansible/blob/v2.2.1.0-1/lib/ansible/module_utils/basic.py#L2223","commit_id":"844a7c87bbee0c10c9a3dc7547ef555c95d3b35b"}]}