The cloud-native orchestrator for the whole development lifecycle, with integrated lineage and observability.

dagster

Assets.png

Sensor__combined_asset_sensor.png

Why is my `combined_asset_job`  from <https://github.com/geoHeil/dagster-ssh-demo/blob/master/SSH_DEMO/sensors/sftp_sensor_asset_real.py#L178> never updating the stale notification in dagit? In the UI I can observe the 3 expected run requests ( for the 3 base assets: foo,bar,baz) as well as for the combined asset. This seems quite strange to me. <http://localhost:3000/instance/asset-graph~*/> shows this problem whereas <http://localhost:3000/workspace/SSH_DEMO@SSH_DEMO/jobs/combined_asset_job> does not indicate a stale asset. Is this a bug in dagit?

Hey <@U01PP2ED4ES> - if you refresh the page, does it update?

But the jobs graph nicely shows the updated version - only the graph in the asset display seems to lag (wich is strange)

if I check out the master branch of your repo and try this out, am I likely to hit the same error?

But if you want I could also jump on a call with you to show you the problem.

I was able to reproduce this with a smaller example. Here's the GH issue: <https://github.com/dagster-io/dagster/issues/7434>