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

Stale Parameters is now not set immediately after put #54

Open
GDYendell opened this issue Nov 15, 2024 · 0 comments
Open

Stale Parameters is now not set immediately after put #54

GDYendell opened this issue Nov 15, 2024 · 0 comments

Comments

@GDYendell
Copy link
Contributor

Now that the subsystems have been split into sub controllers, only the sub system stale parameters is set during the put call and the top level stale parameters is synced in a poll loop. This could cause clients to see that there are parameter updates queued due to the change and won't wait for parameters to be synced before continuing their logic.

Acceptance Criteria

  • The top level stale parameters is set immediately after the put response is received
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Next Sprint
Development

No branches or pull requests

1 participant