Skip to content

Conversation

@shsms
Copy link
Contributor

@shsms shsms commented Nov 8, 2024

The SystemBoundsTrackers send out a new value only when there's a
change in the system bounds. This means when a new receiver is
created, it could wait for a long time before receiving the bounds.

This change allows new receivers to get the latest state when
requested.

This is already the case for battery bounds, and needed only for PV
and EV charger bounds.

The `SystemBoundsTracker`s send out a new value only when there's a
change in the system bounds.  This means when a new receiver is
created, it could wait for a long time before receiving the bounds.

This change allows new receivers to get the latest state when
requested.

This is already the case for battery bounds, and needed only for PV
and EV charger bounds.

Signed-off-by: Sahas Subramanian <[email protected]>
@shsms shsms requested a review from a team as a code owner November 8, 2024 14:13
@shsms shsms requested review from Marenz and removed request for a team November 8, 2024 14:13
@github-actions github-actions bot added the part:data-pipeline Affects the data pipeline label Nov 8, 2024
Signed-off-by: Sahas Subramanian <[email protected]>
@github-actions github-actions bot added the part:docs Affects the documentation label Nov 8, 2024
@shsms shsms enabled auto-merge November 8, 2024 14:19
@shsms shsms added this pull request to the merge queue Nov 11, 2024
@llucax llucax added this to the v1.0.0-rc1100 milestone Nov 11, 2024
Merged via the queue into frequenz-floss:v1.x.x with commit ee58cde Nov 11, 2024
18 checks passed
@shsms shsms deleted the resend_latest_bounds branch November 11, 2024 07:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

part:data-pipeline Affects the data pipeline part:docs Affects the documentation

Projects

Development

Successfully merging this pull request may close these issues.

2 participants