Is there already an issue fix for dagit oddities when multiple repositories provide jobs with the same names? (perhaps related to https://github.com/dagster-io/dagster/issues/8748?) So far, I'm seeing a few cosmetic issues on the main job page/launchpad, where the schedule shown at the top is correct, but the latest run doesn't restrict itself to that repository and is grabbing runs of the same job name from other repositories
forgot to mention: running 1.0.3
Ah, looks like assets are also affected - for jobs that materialize assets, the "View __ assets" button has popped up and points to the job from another repository
The timeline view is behaving oddly as well for job history, in the exact same way - it's displaying a row per job/repository, and then pulling all past runs based on only job
08/17/2022, 11:11 PM
@prha@dish - did you make a fix related to this recently?
08/18/2022, 12:38 AM
Let me know if you need more details or new issues created.
08/18/2022, 1:01 AM
I don’t think I have made a fix related to this recently, unfortunately
08/18/2022, 5:21 PM
Need me to create a new issue then? fwiw, not that big of an unfortunately for us - all of the functionality is clearly working correctly on the backend. it'll be great to get those frontend fixes in, but they're not blocking us from using this job/repository strategy...which is much easier to work with than what we had previously
08/18/2022, 5:34 PM
@Ben Gotow thoughts on this?
08/19/2022, 8:41 PM
Was there a verdict on whether creating a new issue would be helpful or not?