Hi all, I just updated to Meltano v1.64.0 and I f...
# announcements
i
Hi all, 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
d
@ivanovyordan The
ConnectionResetError
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!
I'm able to reproduce the issue locally, thanks for raising this. Let me create an issue.
The issue was indeed introduced in v1.64.0, by https://gitlab.com/meltano/meltano/-/merge_requests/1989.
i
Wow. Thanks so much @douwe_maan That was so fast!
d
I've got a fix working locally as well 🙂 Just applying the finishing touches and it should go out in a release this afternoon
i
That’s really impressive. Congratulations!
d
I'm also happy and impressed that someone in the community (read: you) caught it so quickly 😄