mysterious-train-91935
01/08/2021, 12:30 PMmeltano | Task exception was never retrieved
future: <Task finished coro=<capture_subprocess_output() done, defined at /usr/local/lib/python3.7/site-packages/meltano/core/logging/utils.py:57> exception=ConnectionResetError(‘Connection lost’)>
Traceback (most recent call last):
File “/usr/local/lib/python3.7/site-packages/meltano/core/logging/utils.py”, line 73, in capture_subprocess_output
writer.writeline(line.decode())
AttributeError: ‘StreamWriter’ object has no attribute ‘writeline’
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File “/usr/local/lib/python3.7/site-packages/meltano/core/logging/utils.py”, line 76, in capture_subprocess_output
await writer.drain()
File “/usr/local/lib/python3.7/asyncio/streams.py”, line 348, in drain
await self._protocol._drain_helper()
File “/usr/local/lib/python3.7/asyncio/streams.py”, line 202, in _drain_helper
raise ConnectionResetError(‘Connection lost’)
ConnectionResetError: Connection lost
ripe-musician-59933
01/08/2021, 4:50 PMConnectionResetError
suggests that the target closed its stdin stream prematurely, possibly because it ran into an error and shut down. Do you see any output related to the target ahead of these log lines?
And are you seeing this error consistently when running this pipeline, or only occasionally?
I don't think the lost connection would be caused by v1.64.0, but in earlier versions you would have seen a different error message from a different code path. It's also possible that behind the scenes, the connection would also have been closed/list before, but would not have resulted in an error message at all.
I'll look into it some more, but it'll be good to know if you're seeing this every time, or just sometimes!mysterious-train-91935
01/08/2021, 6:22 PMripe-musician-59933
01/08/2021, 6:22 PMmysterious-train-91935
01/08/2021, 6:23 PMripe-musician-59933
01/08/2021, 6:25 PM