Any ideas what `ELT could not be completed: Cannot...
# announcements
a
Any ideas what
ELT could not be completed: Cannot start tap: Catalog discovery failed:
might be about ? (from tap-spreadsheets-anywhere reading a simple csv file over http)
a
did you see this error when running
meltano elt
from the command line? What happens if you run
meltano invoke tap-spreadsheets-anywhere --discover
?
first thought is that that tap isn't providing valid output when run in discovery mode
d
@andrew_stewart Is
Catalog discovery failed
followed by anything? That error message is coming from either https://gitlab.com/meltano/meltano/-/blob/6a8fae1a9d5a36e936d363389edb9e0038338c44/src/meltano/core/plugin/singer/tap.py#L269 or https://gitlab.com/meltano/meltano/-/blob/6a8fae1a9d5a36e936d363389edb9e0038338c44/src/meltano/core/plugin/singer/tap.py#L295, and in both cases, the output should include a specific error message.
a
I believe I’ve traced the error down to the tap not actually supporting HTTPS protocol. Which is confusing because the README on the tap says it does, but I verified in the code that it only has handlers for s3, ssh, gs and local.
d
Ah, that's unfortunate
a
Related to the above question - I've seen this error before too, and at first I wasn't sure what the actual issue was since the error wasn't surfaced in the UI modal or the log file you can download
I only could see the
Catalog discovery failed
error when running it on the CLI. Is this the intended behaviour?
The error originates here https://gitlab.com/meltano/meltano/-/blob/master/src/meltano/core/plugin/singer/tap.py#L269 I just tried adding a
logging.error
before the exception is raised and then the error does get passed to the job log modal. Let me know if you want me to raise an issue for this
d
@al_whatmough Please do! The full CLI output should always end up in the log file (and modal), so if the error doesn’t, that’s a bug!
a
@douwe_maan no worries, I'll create an issue when I'm back on my laptop! This particular tap was working without error before, but I realise it wasn't outputting a catalog properly when run in discover mode. I only started getting an error in Meltano when upgrading from 1.47 to 1.58 though, so I guess some change between these versions changed the way it handles that type of error