Temporary Query Error on global asset lineage, disappears

[elliottower]

What's the issue?

I'm following the dagster university dbt tutorial, and am getting a weird popup that says Query Error (those exact words, maybe not capitalized? don't remember) on the global asset lineage screen, but then it disappeared after a few seconds. I got it after a failed run, and after a successful run.

I searched the logs in the terminal where I ran dagster dev and didn't find this query error or query anywhere. Not sure how to enable more verbose debugging of the frontend maybe someone can help, or other users have had this issue. Searched and didn't see it.

What did you expect to happen?

No response

How to reproduce?

I'm not 100% sure, tried to reproduce myself and can't seem to. But it reminds me of getting "unexpected GraphQL error" on earlier versions of dagster (#19292)

Dagster version

dagster, version 1.9.6

Deployment type

Local

Deployment details

No response

Additional information

No response

Message from the maintainers

Impacted by this issue? Give it a 👍! We factor engagement into prioritization.
By submitting this issue, you agree to follow Dagster's Code of Conduct.

[garethbrickman]

It's likely there'd be logging for this in your browser's developer tools in the console and/or network tabs