the following snippet is a minimal example for a behavior in version 5.0.3 that I think is a bug:
function noop() {}
Observable.interval(1000).take(1)
.do(() => console.log('step I of first finished'))
.delay(1000)
.do(() => console.log('step II of first finished'))
.subscribe(/* noop, noop, noop */); // uncomment to "fix"
setTimeout(() =>
Observable.interval(1000).take(1)
.do(() => console.log('second finished'))
.subscribe(),
500);
Expected output:
step I of first finished
second finished
step II of first finished
but actually it stops at second finished.
The problem can be worked around by uncommenting the three noop callbacks to the first
subscribe.
The problem was observed in version 5.0.3 -- it has since disappeared and in 5.4.2 it's working just fine.
However, I was unable to connect this to any of the bugfixes mentioned in the changelog and since my client is rather cautious with updating 3rd party libs before the go-live, I'd be very interested to hear if this has explicitly been addressed or if I'm just doing something wrong.
Hi,
the following snippet is a minimal example for a behavior in version 5.0.3 that I think is a bug:
Expected output:
but actually it stops at
second finished
.The problem can be worked around by uncommenting the three
noop
callbacks to the firstsubscribe
.The problem was observed in version 5.0.3 -- it has since disappeared and in 5.4.2 it's working just fine.
However, I was unable to connect this to any of the bugfixes mentioned in the changelog and since my client is rather cautious with updating 3rd party libs before the go-live, I'd be very interested to hear if this has explicitly been addressed or if I'm just doing something wrong.
Thanks in advance and best regards! Markus