and another beginner question ) apparently meltano...
# getting-started
s
and another beginner question ) apparently meltano launches taps in subprocess and in case of error you see only [exit code 1] in the log. then you have to copy (a bit more complicated than just copy) the tap command and launch it again in order to see the real error. any other ways to get to the actual errors? https://meltano.slack.com/archives/CMN8HELB0/p1655148779216659?thread_ts=1655061127.629679&cid=CMN8HELB0
v
Can you show the example of this? Generally you should be seeing the error reported by the Tap when an error happens
a
👍 Also - at least for taps and targets, I think you should see some log files under
.meltano/logs/...
message has been deleted
s
i have a feeling that sometimes logs are missing like in this case (for other cases i indeed could find the logs) may some errors break the logging?
a
Very possible. If so, we definitely would want to log as an issue/bug.
Ideally, we'd be logging output for all commands, even the setup hooks like catalog discovery.
s
going to reproduce the error a bit later and create the issue thanks
c
I am calling meltano like this print all debug info to the output
meltano --log-level=debug invoke tap-spreadsheets-anywhere --discover
. It has helped me lots with some issues (Others would require extra work 😄 )