Add volatility property to CachingStaleStatusResolver

[smackesey]

Summary & Motivation

• Add _is_volatile on CachingStaleStatusResolver.
  • This required exposing observability on AssetGraph.
• Remove StaleRootCause, which is dead code that should've been previously removed.

How I Tested These Changes

BK

No new tests since this property is at present internal to the CachingStaleStatusResolver and not used for anything. Testing will be done on the outputs of CachingStaleStatusResolver that volatility informs.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

2 Ignored Deployments

Name	Status	Preview	Comments	Updated
dagit-storybook	⬜️ Ignored (Inspect)			Mar 9, 2023 at 9:56PM (UTC)
dagster	⬜️ Ignored (Inspect)			Mar 9, 2023 at 9:56PM (UTC)

[smackesey]

Current dependencies on/for this PR:

• master
  • PR Add volatility property to CachingStaleStatusResolver #12855 👈

This comment was auto-generated by Graphite.

[OwenKephart]

would be good to put some common situations under test but the logic looks good

[smackesey]

would be good to put some common situations under tes

Prefer to avoid this atm since right now _is_volatile is just an implementation detail of CachingStaleStatusResolver. If we expose it, then I would support testing it directly the way the public API is tested