Has anyone seen this error before? I am getting th...
# getting-started
d
Has anyone seen this error before? I am getting this on multiple taps. Any help would be appreciated!
Copy code
ELT could not be completed: Cannot start extractor: Catalog discovery failed: command ['/workspaces/hs-meltano/tap-clickup/tap-clickup.sh', '--config', '/workspaces/hs-meltano/tap-clickup/.meltano/run/elt/2021-11-09T194635--tap-clickup--target-snowflake/3e76b134-9f1d-481c-9404-3306c225ed7b/tap.bac0c6fd-35f9-4f76-8116-e4d7445e8a2a.config.json', '--discover'] returned 1
v
@aaronsteers we need an auto responder or something for this error 😄 @drew_ipson it's an error happening during discovery. If you run the tap in debug mode that will help you out. Here's things that would help tremendously 1. A repo with your Meltano project (not needed but would be easier) (Optional with 2 and 3 below) 2.
meltano.yml
file 3. command you're running to get the error
a
Also - @drew_ipson - can you rerun with --log-level=debug? This may produce helpful output regarding auth and/or config options.
d
@derek_sanz Sure thing! I can do 2 & 3:
Copy code
2. meltano elt tap-clickup target-snowflake
v
ooo clickup 😄 throw --log-level debug in as an option with meltano so
Copy code
meltano --log-level=debug elt tap-clickup target-snowflake
d
Sure thing. I’ll also get you my meltano.yml file as well
Copy code
version: 1
send_anonymous_usage_stats: true
project_id: 9a1b585d-349d-4004-836e-b14504a82a49
plugins:
  extractors:
  - name: tap-clickup
    namespace: tap_clickup
    executable: ./tap-clickup/tap-clickup.sh
    capabilities:
    - state
    - catalog
    - discover
    settings:
    - name: username
    - name: api_token
      kind: password
    select:
    - '*.*'
    config:
      api_token: <REMOVED>
      start_date: '2021-11-08T00:00:00Z'
@visch @aaronsteers Here’s the error thrown and the meltano.yml file is above.
v
I can tell what the error is from the meltano.yml file, but I have no idea why the error is so cryptic. @aaronsteers any ideas there on how we can make this easier? @drew_ipson the steps https://meltano.com/tutorials/postgres-with-postgres.html#adding-a-custom-extractor go through how to add a custom extractor. How'd you land on
Copy code
- name: tap-clickup
    namespace: tap_clickup
    executable: ./tap-clickup/tap-clickup.sh
?
d
@visch I was following the installation steps in your README and got some error spitting out that the tap-clickup.sh file could not be found, so that was my fix. Looking at these docs helps a ton with that.
v
Got it! I'll put an issue in the clickup readme to help out for Meltano users. I also threw in https://gitlab.com/meltano/hub/-/issues/161 which may be helpful as wel
Did you change to using
pip_url
instead of
executable
then?
d
Yes, that would be awesome! Thanks for adding that, Derek. That is correct - I also switched to the pip url.
v
awesome, so
pip_url
then ran
meltano install
and dancingpenguin
d
Yes! dancingpenguin
@aaronsteers any ideas on the ascii error?
a
@drew_ipson - By chance are you running on hybrid windows/wsl? I can see the file path in your screenshot was a linux path, but the error points to some kind of encoding/decoding issue - which could be caused by a file encoded for windows being shared to linux. (Or some entirely different root cause.) Some google research does point to a mismatched character encode/decode somewhere. Can you post the full log so we can see better where the error is being generated from?
Python hackery seems to hint at a latin1 encoded character.
Copy code
>>> b'\xe2'.decode('latin1')
'â'
>>> b'\xe2'.decode('utf-8')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe2 in position 0: unexpected end of data
>>> b'\xe2'.decode('ascii')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 0: ordinal not in range(128)
d
@aaronsteers Sure thing — I am running my Meltano Docker image inside VS Code Remote Container, which is why you see that path show up the way it is. I get this discovery failure error from directly inside my container and inside VS Code remote-container.
a
Is that a yes to the Windows question also? Perhaps there's a volume being shared (
.meltano
for instance) with files being passed between Windows and Linux. In that case, a windows-run task may have written files in a way that the linux-run processes are not able to read it. (Just a theory.)
d
@aaronsteers Apologies — no I’m running a Mac.
a
Ah, okay. Thanks for confirming. I'm not sure what would cause that error but I'd like to confirm if it is coming from the tap or coming from Meltano. The full log (from command to the bottom) might be helpful. It might also would be helpful to know if you're able to invoke the tap on its own.
d
Thank you for the help! I’ll keep at it and let you know if I find anything of note
a
Great thanks! This came up recently also - related to a tap that was getting upstream data in non-standard (non-utf8) encoding, and then passing it along to the target, which could not properly parse it. Might be related or not, but wanted to share just in case.
f
One thing I have seen, which I do not know is related in any way but thought I'd mention it, is that some taps behave differently based on whether a configuration/catalog is provided as input or not. If none is provided, the tap will/should do a full discovery. If one is provided, different things can happen depending on how it is written. I see that there was a
select: "**.**"
in the config. That would be the something provided case. I believe that is the default, no?