Extending existing pipeline, and suddenly tap-gith...
# troubleshooting
j
Extending existing pipeline, and suddenly tap-github stopped work for me. Config screenshot below. I execute:
Copy code
meltano --environment cicd_dev run tap-github-repo target-snowflake
It fails:
Copy code
023-02-21T13:59:48.317777Z [error    ] Cannot start plugin tap-github-repo: Executable 'tap-github' could not be found. Extractor 'tap-github-repo' may not have been installed yet using `meltano install extractor tap-github-repo`, or the executable name may be incorrect.
I bumped version of Meltano to the latest 2.15.3, recreated
venv
, but it is still failing. In Gitlab, where I use v2.12 (based on your Docker image), the same
meltano.yml
works. Any clue?
w
You can use:
Copy code
executable: tap-github
Just add this under the inherit_from setting
And if it is still not workingtry to install the child extractor (don't know why we should do this though)
j
executable does not help
strange, I downgraded meltano do 2.12, which works for me in Gitlab pipeline, and it does not help, it is still failing with the same error
Any advice how to debug this issue would be much appreciated
True is that the
tap-github
executable really does not exist, if I install the tap with
meltano install
I have solution!
rm -rf .meltano
Looks like when you play with meltano in a venv, e.g. you bump the version, it can lead to these issues. In the pipeline, a Gitlab worker starts from scratch from an image, so this issue can't happen there 😉
s
@jan_soubusta My solution for any of these issues is to have all my projects (not just Meltano) super stateless. I start with a fresh dockerized dev setup multiple times a day. That kind of forces me to make sure I don't inject some dependencies somewhere I'm not aware of.
j
A good habit to work around the issue, but I still think it should not behave like this. Personally, I have not faced such an issue with any other PyPI package - upgrade of version should not break it like this, IMO.
s
Hm @edgar_ramirez_mondragon are you able to see the problem here? I know it's solved, but I would like to know whether there is either a possible fix for this or a best practice that makes sense to put somewhere?
e
I think
meltano install --clean
should also have worked