You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 7, 2021. It is now read-only.
Got an example of a stream with dupes? I have seen a few initial events with empty collections we should be able to filter out.
We do join quite a few streams together with combineLatest (e.g. Deployment + Service - or now Deployment + Service + Route) so that the main object may appear mostly similar (e.g. the Deployment) on multipole events but we enrich with the exposeUrl so we can link to how to open the web app/REST API of a deployment - so it might look a dupe but might not be if you look really close?
For example deploymentStore.loadAll() emits about 10-15 times in quick succession, slowly building up the model. This is without any changes to anything. I would expect a single emission here. Whilst the emissions may not be technically duplicates, as a consumer of the API I shouldn't see them.
Right now I just debounce the stream for about 300ms to get the last one, but this is sucky.
yeah - Deployment is the trickiest one as its joining Deployments + DeploymentConfigs + Services + Routes + ActiveRoute namespace. I'm pretty sure we're unnecessarily exposing events on startup though too
I'm seeing multiple identical events being sent down streams. Normally this is caused by a lack of multicast support.
The text was updated successfully, but these errors were encountered: