-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unsubscribing and timer #67
Comments
By the way, I'm using this gist for the timer: https://gist.github.com/natecook1000/b0285b518576b22c4dc8 |
Hi, So AutoDetach observer was in place and it was disposing in case of sequence was completed, but in case you didn't dispose producer, it would pass events until producer was disposed. Problem was here
I can fix this, add additional unit tests and push this to develop branch. This doesn't seem to me like a critical issue, so are you ok just using develop branch code until next release until this enters master branch? |
Hi, thanks for the fast response. It's ok, I'm just learning, so I'm not in a hurry. It just helps to know it wasn't me doing something wrong. I'll keep an eye on the fix to see if I can understand what was going on :) |
I think I am experiencing this bug, too... but with |
The fix should be in develop commit 24dc2c6
@alcarvalho send me all heisenbugs 😛 |
These changes have been released in the latest release. Closing this issue. Let me know if it happens again. |
I'm trying to translate to RxSwift an example in the "Intro to Rx" web.(http://www.introtorx.com/Content/v1.0.10621.0/04_CreatingObservableSequences.html down where it creates a Timer)
This is what I have:
I'm trying to unsubscribe while keeping the timer running (as the example does) and then invalidate the timer in the dispose block (by uncommenting the "timer.invalidate()" line) to demonstrate the use of the disposable for cleaning purposes.
The problem is, with the code as it is, after the 3 seconds passed, the timer is still running (as expected) but the subscription seems to be active as well.
This is what I get:
If I invalidate the timer, of course, I stop receiving events, but it seems I'm not unsubscribing for some reason.
The text was updated successfully, but these errors were encountered: