When tap finishes before target, not all messages (records) actually make it to target but `meltano elt` succeeds anyway
The only indication that anything went wrong is a ConnectionResetError: connection lost
in the meltano elt
output/logs.
As reported by Yordan Ivanov on Slack:
I just updated to Meltano v1.64.0 and I faced an error. I wonder if it’s because I do something wrong, or It’s a bug in the new version. Here’s the stack trace
meltano | 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
This was introduced by !1989 (merged) which was released in v1.64.0.
Edited by Douwe Maan