Hello, I'm getting some weird behavior with meltano. I'm trying to test my custom tap from meltano\taps\custom-tap, but it's failing when I run

meltano run custom-tap

with no stack trace. However, it's letting me invoke the tap and prints out data on my CLI when I do a

meltano invoke custom-tap

. I have some other custom commands for my utilities and those are failing too. My laptop recently backed up to OneDrive, and my project was previously at C:\Users\user\Documents\GitHub\datawarehouse\meltano, but then got moved to C:\Users\user\OneDrive - Company\Documents\GitHub\datawarehouse\meltano and it looks like the other documents folder got deleted. I'm assuming this is the cause of the issue since I never encountered this error before, and meltano throws an error when i try to run my custom commands that basically says it can't find meltano.exe in that first directory (because it's not there). Has anyone experienced this? Should I just recreate the Documents\GitHub directory in my user drive and then clone the repository there?

Can you share the output you get? If you move drives you do have to re-run

meltano install

If you not getting any output at all you could add debug logging with your command

meltano --log-level=debug run custom-tap target-jsonl

2024-04-18T175128.255827Z [info ] Environment 'test' is active 2024-04-18T175129.277931Z [error ] Loader failed 2024-04-18T175129.278923Z [error ] Block run completed. block_type=ExtractLoadBlocks err=RunnerError('Loader failed') exit_codes={<PluginType.LOADERS: 'loaders'>: 1} set_number=0 success=False Need help fixing this problem? Visit http://melta.no/ for troubleshooting steps, or to join our friendly Slack community. Run invocation could not be completed as block failed: Loader failed This is the output that I'm getting from it. I've already rerun

meltano install

You can always try the classic: https://meltano.slack.com/archives/C069CQNHDNF/p1709285783399029?thread_ts=1709281880.649789&amp;cid=C069CQNHDNF

Yeah, my suspicion is there's something off in the tap's output. Running at debug level should display the target's traceback and give us more clues.