-
Notifications
You must be signed in to change notification settings - Fork 228
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
notifier returned by makeNotifierFromAsyncIterable is lossless #5413
Comments
gibson042
added a commit
that referenced
this issue
Jun 30, 2022
gibson042
added a commit
that referenced
this issue
Jul 8, 2022
gibson042
added a commit
that referenced
this issue
Jul 8, 2022
gibson042
added a commit
that referenced
this issue
Jul 8, 2022
turadg
pushed a commit
that referenced
this issue
Jul 8, 2022
turadg
pushed a commit
that referenced
this issue
Jul 8, 2022
turadg
added a commit
that referenced
this issue
Jul 12, 2022
mergify bot
added a commit
that referenced
this issue
Jul 14, 2022
* fix(notifier): Make makeAsyncIterableFromNotifier lossy Cherry-picked from gh-5413-lossy-makeNotifierFromAsyncIterable. See #5695 . * fix(notifier): Revert "Make makeAsyncIterableFromNotifier lossy" Eager consumption led to infinite loops; see #5695 for context. * feat(notifier): Add makeNotifierFromSubscriber Fixes #5413 * test(notifier): Update per code review * chore(notifier): Resolve lint warnings * fix(notifier): Align makeNotifierFromSubscriber with makeNotifierKit getUpdateSince() always consults the source subscribeAfter() rather than using a possibly-stale local cache. * fix master merge Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> Co-authored-by: Turadg Aleahmad <turadg@agoric.com>
turadg
added a commit
that referenced
this issue
Jul 14, 2022
* fix(notifier): Make makeAsyncIterableFromNotifier lossy Cherry-picked from gh-5413-lossy-makeNotifierFromAsyncIterable. See #5695 . * fix(notifier): Revert "Make makeAsyncIterableFromNotifier lossy" Eager consumption led to infinite loops; see #5695 for context. * feat(notifier): Add makeNotifierFromSubscriber Fixes #5413 * test(notifier): Update per code review * chore(notifier): Resolve lint warnings * fix(notifier): Align makeNotifierFromSubscriber with makeNotifierKit getUpdateSince() always consults the source subscribeAfter() rather than using a possibly-stale local cache. * fix master merge Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> Co-authored-by: Turadg Aleahmad <turadg@agoric.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
The design of Notifier is that if you call
getUpdateSince()
without any arguments, you get the latest state.This is different for the alleged Notifier returned by
makeNotifierFromAsyncIterable
. It never skips elements of the iteration of the underlying subscription.Expected behavior
A
Notifier
skips states consistently. EithermakeNotifierFromAsyncIterable
conforms or is renamed. (Or replaced if there's something better.)The text was updated successfully, but these errors were encountered: