Skip to content
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

Add status change event #3903

Open
wants to merge 5 commits into
base: main
Choose a base branch
from
Open

Commits on Feb 1, 2024

  1. Rename 'status' to 'cluster_load' event stream.

    This allows to avoid confusion with upcoming status change event stream.
    
    Signed-off-by: Yevhen Vydolob <[email protected]>
    evidolob committed Feb 1, 2024
    Configuration menu
    Copy the full SHA
    a04f52c View commit details
    Browse the repository at this point in the history
  2. Add events implementation

    It allows us to have unified way to propagate state changes across an app
    
    Co-Authored-By: Christophe Fergeau <[email protected]>
    Signed-off-by: Yevhen Vydolob <[email protected]>
    evidolob and cfergeau committed Feb 1, 2024
    Configuration menu
    Copy the full SHA
    0b8ec64 View commit details
    Browse the repository at this point in the history
  3. Add "NoVM" state

    This would simplify podman-desktop ext status handling
    
    Signed-off-by: Yevhen Vydolob <[email protected]>
    evidolob committed Feb 1, 2024
    Configuration menu
    Copy the full SHA
    6d61cbf View commit details
    Browse the repository at this point in the history

Commits on Aug 7, 2024

  1. Add status change event

    Will propagated to client via SSE in ith own channel, to inform clients about CRC status change.
    Status modified in "status_change_stream.go", as current status implementation has no single point of change, so tracking transition between states is challenging.
    
    Signed-off-by: Yevhen Vydolob <[email protected]>
    evidolob committed Aug 7, 2024
    Configuration menu
    Copy the full SHA
    1029bb7 View commit details
    Browse the repository at this point in the history
  2. Fix logging channel messages.

    Having '\n' character in between message field is braking SSE specification and client could not parse correctly such events
    
    Signed-off-by: Yevhen Vydolob <[email protected]>
    evidolob committed Aug 7, 2024
    Configuration menu
    Copy the full SHA
    66237fa View commit details
    Browse the repository at this point in the history