Closed alexluong closed 6 months ago
Hi @leggetter, thanks for catching this issue. This happened because your source has a few different connections and some connections do not lead to a CLI destination. With the refactor, the data shape is a bit different so the way we check whether a destination is CLI or not led to the invalid memory address issue. I have updated the logic to account for this case.
Can you check and see if the CLI behaves as expected now?
@alexluong - trying this locally and getting an error on this command where I'm passing the
source
name ofinbound
as an argument:You can see the sources I have available here:
Here's how the version 0.8.6 of the CLI behaves: