Repository navigation
[Bug]: AutoRefreshOnObservable produces refreshes for immediately-removed items #1099
Description
Feeding the following sequence of changesets into .AutoRefreshOnObservable() (for the cache version, the list version doesn't seem to have this issue, it just emits an empty changeset), when the refresh observable emits a value immediately upon subscription, results in the following downstream sequence changesets, which includes an invalid Refresh for an item that was previously removed from the collection.
Upstream
2 Changes
Add #1
Remove #1
Downstream
2 Changes
Add #1
Remove #1
1 Change
Refresh #1
If the upstream changeset is split up to have the Add and Remove be in separate changesets, there is no issue, as follows:
Upstream
1 Change
Add #1
1 Change
Remove #1
Downstream
1 Change
Add #1
1 Change
Refresh #1
1 Change
Remove #1
This doesn't seem to be an issue with any of the operators used internally within AutoRefreshOnObservable() (E.G. .MergeMany() and .SubscribeMany()), but with the sequencing of subscriptions within .AutoRefresh() itself.
I discovered this while expanding our testing suite for .FilterOnObservable(), which ends up occasionally including items in its downstream that were removed upstream.
Activity
Rewrote testing for the cache variant of the AutoRefresh() and AutoRe…
Rewrote testing for the cache variant of the AutoRefresh() and AutoRe…
Rewrote testing for the cache variant of the AutoRefresh() and AutoRe…
Rewrote testing for the cache variant of the AutoRefresh() and AutoRe…
Rewrote testing for the cache variant of the AutoRefresh() and AutoRe…
Refactor cache operators onto Orchestrator composition primitive
Add CacheChangeHandlerBase, eliminate ScheduleEmit
AutoRefresh: unify buffered/unbuffered, fix stale-refresh hazard
Rewrote testing for the cache variant of the AutoRefresh() and AutoRe…
JakenVeina commentedon Oct 14, 2026
Should be fixed now in 9.5.
github-actions commentedon Oct 28, 2026
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.