Is there a way to suppress or limit the massive stack trace that gets thrown out when

meltano run

fails? I just want a concise summary of what failed with the tap/target (without Meltano stack frames).

So maybe https://github.com/meltano/meltano/issues/6728#issuecomment-2099504354

I've never really understood why all the meltano stuff comes through here, haven't dove in either so I"m sure there's a reason but in my head and custom implementations of

tap | target

I"ve done if the tap/target fails you print the stdout/stderr that comes from that tap or target and then the orchestrator (meltano) says Extractor failed with exit code (1) or whatever it failed with and then you're done, I don't get the need for Meltano traces when the Meltano process didn't fail.

Tbh I don't know under what conditions the stack trace explosion shows for - doesn't seem to happen for config validation or request failures, maybe unhandled errors? I find the whole logging setup quite confusing, but I don't think I'm the target audience either. I guess I would just like the default behaviour to be not as verbose - I'm fine with the format and we can already control log level without touching logging config.

When I dove on this early I found that run does behave the way I'd expect it to. There's conditions where meltano itself fails and does the whole huge stack trace thing and I think that's the issue here

FWIW it was a

meltano run

command that caused this (

v3.5.4

), albeit quite a few plugins/commands. cc @daniel_walker