-
Notifications
You must be signed in to change notification settings - Fork 5
Fetch dispatches in sync with periodic reconnect of client.stream #155
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
base: v0.x.x
Are you sure you want to change the base?
Conversation
ba62a7a
to
a79b3e3
Compare
To ensure we didn't miss any. Signed-off-by: Mathias L. Baumann <[email protected]>
a79b3e3
to
b5aff78
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, only needs rebasing :)
Unfortunately, using a new base-client also means allowing a new base client version in microclient, so we will have to release both base-client and microclient |
"microclient" 😆 |
await self._lifecycle_events_tx.send(Deleted(dispatch=dispatch)) | ||
match selected.message: | ||
case StreamStartedEvent(): | ||
_logger.info("Dispatch stream restarted, refreshing dispatches") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"(re)started"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Realistically we never will get the start notification because we create the new_receiver()
only after it was sent
Should probably use
frequenz-floss/frequenz-client-base-python#141
eventually to be less hacky?