Hey Everyone, Some context: OS: Ubuntu in WSL2 fo...
# troubleshooting
j
Hey Everyone, Some context: OS: Ubuntu in WSL2 for Windows I'm experiencing a very strange permissions issue related to a custom tap that I built. I have added the tap to my meltano project and successfully installed this tap and the others in my project using
meltano install
many times, invoked it alone, utilized it in a
meltano run
pipeline, etc. The project repo on github was transferred to an organization account (it seems that this was the root cause of the issues outlined below). I transferred the repo back to my user account, thinking this might resolved the problem. The issue is that now when I go to install the custom tap I get the following error message:
Copy code
jcohen@WIN-10-COHEN:~/meltano-dev/etl-overhaul-testing$ meltano install extractor tap-progressopenedge
Installing 1 plugins...
Installing extractor 'tap-progressopenedge'...
Need help fixing this problem? Visit <http://melta.no/> for troubleshooting steps, or to
join our friendly Slack community.

[Errno 13] Permission denied: '.gitignore'
I have no trouble installing other standard taps in my project:
Copy code
jcohen@WIN-10-COHEN:~/meltano-dev/etl-overhaul-testing$ meltano install extractor tap-postgres
Installing 1 plugins...
Installing extractor 'tap-postgres'...
Installed extractor 'tap-postgres'
Troubleshooting performed thus far: • I've checked the file permissions on the .gitignore file and they haven't changed (though it's unclear from the error which .gitignore file is causing the issue). • I've ensured I'm authenticated with github using the GitHub CLI • I've removed, and re-added the custom tap. • I and another person testing the tap have tried to install the tap in a project on the windows OS receiving the following error:
Copy code
ERROR: HTTP error 404 while getting <https://github.com/Jcohen010/tap-progressopenedge.git>
ERROR: Could not install requirement <https://github.com/Jcohen010/tap-progressopenedge.git> because of HTTP error 404 Client Error: Not Found for url: <https://github.com/Jcohen010/tap-progressopenedge> for URL <https://github.com/Jcohen010/tap-progressopenedge.git>
I'm not sure how to resolve this issue, I hope someone has some useful insights. Thanks guys! Justin
So changing the repo to public resolved the 404 error we were experiencing and allowed me to install the tap successfully on windows, but the change had no effect on the
[Errno 13] Permission Denied
error
e
I'm able to do
meltano install
after adding that as a custom plugin, so it's probably something to do with WSL.
j
Hm, for some reason, I created a whole new project from scratch and installed the tap just fine...
I haven't had the greatest experience with WSL, as it seems to be the case with many others; what would be the best approach to using meltano on a windows machine? I would assume docker or another containerization service?
e
@visch might know better
v
wsl works good but keep file system stuff seperate to windows and you'll be ok. re https://learn.microsoft.com/en-us/windows/wsl/filesystems#file-storage-and-performance-across-file-systems For what happened to you it's hard to tell without seeing your meltano.yml but a real simple fix is
meltano install --clean
which wipes out the out files that were around for your
venvs
another easy option is to just
rm -rf .meltano
To dive into your error you had I'd isolate it down to a single action that's happening, and then almost certainly you have some kind of file permissions going on
ls -lsa
is normally all you need to dive in and figure it out
j
So I tried running
rm -rf .meltano
and it turns out the custom taps venv directory inside the .meltano folder somehow had its permissions changed as all other venvs in the project were deleted accept to that one, which returned permission denied errors. I manually deleted the tap's venv and successfully reinstalled it without any issue. Any idea how that could happen?
And thanks @visch for the resources on WSL, I'll check them out
v
It would only happen from something you did Justin so I don't know! Could be a run on the same folder from inside windows instead of wsl, I'm not sure