hey y’all waves i’m running into an issue with the invoiced tap. the interesting thing is that it has worked with no issues for months. something changed an hour or so ago that is causing the following:

root@meltano-ui-deployment-76dcd75879-pgplh:/project# meltano --log-level=debug invoke tap-invoiced
2022-10-05T18:49:35.387581Z [info     ] Environment 'prod' is active
2022-10-05T18:49:37.166100Z [debug    ] Creating engine ...
2022-10-05T18:49:37.410473Z [debug    ] loaded lazy attr 'SafeConfigParser': <class 'configparser.ConfigParser'>
2022-10-05T18:49:37.410653Z [debug    ] loaded lazy attr 'NativeStringIO': <class '_io.StringIO'>
2022-10-05T18:49:37.410785Z [debug    ] loaded lazy attr 'BytesIO': <class '_io.BytesIO'>
2022-10-05T18:49:38.529907Z [debug    ] Encoding detection: ascii is most likely the one.
2022-10-05T18:49:40.109154Z [debug    ] Invalid URL 'https:/hub.meltano.com/meltano/api/v1/plugins/extractors/tap-invoiced--singer-io': No host supplied

why/where is the hub url getting transformed to remove an

/

after

https

?

we're having the same problem as of a little bit ago. cc: @TomasB

Thanks for reporting this @rafa. We're aware of the issue, and are currently working to resolve it ASAP. I'll let you know here when it has been fixed. Sorry for the trouble.

Hi folks, this should be fixed now

@edgar_ramirez_mondragon, what was the issue?

Bad urls returned by the Meltano Hub API. @chris_stout @rafa that makes me wonder, are you using lock files? The broken Hub shouldn’t be causing issues for

meltano invoke

if the plugin definition is locked 🤔

we haven't locked them. Maybe we should so we don't run to this issue again

same here

In our (Chris and I) case though, we had issues building the docker image and it was failing on

meltano install

step

fwiw, i didn’t catch the issue with

meltano invoke

. it was the orchestrated

meltano elt

command that failed. i used invoke to replicate the issue. but in either case, i’m not using lock files.