KeyError raised when CachingStaleStatusResolver fails to find asset key associated with a dbt 'source' in v1.6.7+ about dagster HOT 4 OPEN

Hi @the4thamigo-uk, AssetGraph (which as you note is a private API) is under very heavy surgery right now, so it's not surprising you're seeing problems. There is a fresh batch of changes that will roll out next week that includes performing "normalization" on the assets defs passed in to the AssetGraph, which will create stub defs for any referenced asset keys otherwise lacking a def-- I'm guessing that is going to fix your problem here, so my advice is to try upgrading to next week's release.

Let's leave the issue open until then and revisit if that doesn't work.

there doesn't seem to be a publicly-exposed way to request the stale status of a given asset/partition.

That's a good point, the closest thing we have is the GQL API. I'm going to put adding a Python API for this in our internal queue.

from dagster.

Thanks @smackesey ... sounds good...

from dagster.

Looks like the 1.6.9 release might have fixed this, was that expected?

from dagster.

Looks like the 1.6.9 release might have fixed this, was that expected?

It wouldn't be surprising, since AssetGraph is under heavy surgery. Since it's a private API I can't recall exactly which changes are falling into which release.

from dagster.