I keep running into an issue where my

tap-mssql

job hangs after uploading state to blob storage. I've tried editing the state file, deleting the container, and nothing is working and the job still hangs at this step: 125447.946 PM gp INFO 2025-10-17T165447.946654Z [info ] Reading state from Azure Blob Storage 125448.028 PM gp INFO 2025-10-17T165448.027881Z [info ] uploading part #1, 17 bytes (total 0.000GB) Has anyone run into this? Any ideas? The file itself in Blob Storage IS being updated with the correct replication key, so I've got no idea why this is failing.

pip_url: dagster-ext==0.1.3 dbt-core==1.9.3 dbt-snowflake==1.9.3 dagster==1.9.7

this is my dagster version if it matters

something is hanging so you have to figure out why. I've seen a lot of folks muff sub processes with their Meltano calls, I've seen tap's hanging. Easiest is to throw a debugger in and figure out where it's getting hung exactly in the stack

So just set this and try again? _MELTANO_CLI_LOG_LEVEL='debug'_

@Ian OLeary are your other jobs using azure state running successfully? Is it just this combination of state and tap, or any combination?

I mean something like this @Ian OLeary https://dagster.io/blog/interactive-debugging-with-dagster-and-docker

@Andy Carter My other jobs using Azure state were running successfully, and it appears that stream seems to have resolved itself over the weekend.

ahhh nice you found it! https://github.com/BuzzCutNorman/tap-mssql/issues/76 would solve it if you want to run with it!

if self.config.get('fake_it', False):

so setting this in config to True?

Yes, tap postgres has this already with filter schemas I think it would translate maybe even 1:1 I'm not sure

But if there's tables in the same schema as the table I'm trying to replicate and i filter it out - wouldn't it break that stream?