https://linen.dev logo
Join Slack
Powered by
Hey everyone - I have run into some kind of wild s...
# troubleshooting
j
Hey everyone - I have run into some kind of wild scenario on my local environment where the 
dbt-snowflake
extension just decided to stop working entirely. Details in 🧵
I am using a Windows environment, and am currently on the dbt-snowflake 1.7 versions and now trying to use 1.8 to stay latest. When I updated my versions and ran 
meltano install --clean
, I get this stack trace
ErrorRunningDBT.txt
This error persists now even if I undid all of my changes, and did a fresh 
meltano install --clean
back on 1.7.0. I have also tried to reinstall meltano itself (on V3.4.2) and on my main branch with no changes it continues to produce the same stack trace. I AM able to run 
meltano
normally though with selecting taps and targets.
And what is more interesting to me is that my container still works. I re-built my container and logged into it running the same command, and it executes as expected
I have also tried running the dbt snowflake in v1.8+ and it works in the container as well
this is what my meltano.yml file looks like for dbt right now
Copy code
plugins:
  utilities:
  - name: dbt-snowflake
    variant: dbt-labs
    pip_url: dbt-core~=1.7.0 dbt-snowflake~=1.7.0 git+<https://github.com/meltano/dbt-ext.git@main>
    commands:
      parse_manifest:
        args: parse --quiet
        executable: dbt_invoker
So yeah, I've tried reinstalling python, reinstalling pip, reinstalling pipx, and reinstalling meltano and even recreating my repository in github. I'm still running into the same stack trace.
I'm wondering if there's any cached information that meltano or python is storing somewhere that is causing everything to go haywire
v
Copy code
File "C:\Git\elt-pipeline\.meltano\utilities\dbt-snowflake\venv\Lib\site-packages\meltano\edk\process.py", line 137, in _exec
    loop.add_signal_handler(
  File "C:\Program Files\Python311\Lib\asyncio\events.py", line 578, in add_signal_handler
    raise NotImplementedError
Is the issue. So the EDK version is calling something that's not implemented on Windows would be my guess. So maybe the EDK version for dbt-snowflake isn't hard tied to a specefic version and there was a breaking changing in between your runs? If you could tie to the EDK version that worked for you you could probably get this going again while you look for a better fix!
There it is
Update your pip url to have this, but change the @ to match a version that worked for you of the dbt-ext. We should follow up here with a Meltano hub issue to look into something better I'm just trying to help get you running! git+https://github.com/meltano/dbt-ext.git@main
Hope that helps I'm busy jumping to a few things so I can't explain in more depth with a fix, but should give the right crumbs as the dbt-ext is tied to the meltano edk
j
Ya I changed that pin from 
@main
to be 
@v0.1.0
and now DBT is running again.
dancingpenguin 1
❤️ 1
Thank you so much Derek, was bashing my head late last night trying to figure things out
Should I put an issue under https://github.com/meltano/edk/issues ?
i
@joshua_janicas thanks for posting this q - was running into the same issue
➕ 2
j
I made a blurb here https://github.com/meltano/edk/issues/264 of the issue
@Edgar Ramírez (Arch.dev) If there's any other insight I need to provide here, or if this is the wrong repo to post that issue in, please let me know!
👀 1
v
@joshua_janicas yeah I think that sounds right to me!
If you could throw up a PR they'd be even happier 😄 but just this is great
e
Thanks for logging the issue! I'd appreciate a PR since I don't have a Windows machine handy to test the proposed solution.
j
Ok, if no one else is able to tackle it in a bit I can try to take a look
b
Hi, thank you all! Our team was facing the same issue with dbt-bigquery. Changing main to 
@v0.1.0
helped
2 Views
Open in Slack
PreviousNext
Powered by