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
…ing case
Resolves an edge case where if a user provided a synchronous source and a synchronous notifier, using a trailing behavior, the returned observable would get caught in a loop emitting the final value over and over again.
fixes: ReactiveX#6058
…ing case (#6059)
Resolves an edge case where if a user provided a synchronous source and a synchronous notifier, using a trailing behavior, the returned observable would get caught in a loop emitting the final value over and over again.
fixes: #6058
Originally reported here
Original Text (@OliverJAsh)
Another weird discovery: in v7.0.0-beta.10 this doesn't throw an error but it does still log
1
over 1000 times.https://stackblitz.com/edit/rxjs-compat-vswz6n
If someone can confirm this is not expected behaviour, I can try to send a PR with a test and a fix.
If I understand correctly, this is the expected behaviour as @josepot says:
So
source
should emit nothing and complete synchronously?Ah, I believe this is because of this change: 4af0227. In my example the duration selector never emits anything, it only completes. That makes sense.
The text was updated successfully, but these errors were encountered: