BlueskyRun inherits from Catalog.
RemoteBlueskyRun, despite the name, does not inherit from BlueskyRun, rather from RemoteCatalog.
In Xi-CAM, we have an issue where the Preview panel fails to paint when the configured catalog is a intake-server because we see RemoteBlueskyRun and are expecting to see a BlueskyRun. Xi-CAM/Xi-cam#13
Xi-CAM couldn change this by switching our signal to either Catalog or object and do the isinstance checking ourselves every time. But perhaps there could be a common base class in this case so that all consumer could know that they have a Catalog that's a Run, coming from Bluesky?
BlueskyRun inherits from Catalog.
RemoteBlueskyRun, despite the name, does not inherit from BlueskyRun, rather from RemoteCatalog.
In Xi-CAM, we have an issue where the Preview panel fails to paint when the configured catalog is a intake-server because we see RemoteBlueskyRun and are expecting to see a BlueskyRun. Xi-CAM/Xi-cam#13
Xi-CAM couldn change this by switching our signal to either Catalog or object and do the isinstance checking ourselves every time. But perhaps there could be a common base class in this case so that all consumer could know that they have a Catalog that's a Run, coming from Bluesky?