8000 Health Check: Remember last status per category by work-lto · Pull Request #1508 · eclipse-scout/scout.rt · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Health Check: Remember last status per category #1508

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

Open
wants to merge 2 commits into
base: releases/23.2
Choose a base branch
from

Conversation

work-lto
Copy link
Contributor
@work-lto work-lto commented May 8, 2025

419786

@avandorp
Copy link
Member
avandorp commented May 8, 2025

[EDIT: Resolved with new commit] Thanks! Shouldn't we either have the timestamp per category in the map or invalidate the map on every put operation? Now one could query for category 1 and subsequently for a long time for category 2 and then get a stale answer for category 1.

@eclipse-scout-bot
Copy link

Can one of the admins verify this patch?

@@ -169,12 +174,21 @@ else if (m_timeout > 0 && m_futureStart + m_timeout < System.currentTimeMillis()
* @param result
* status of last executed health check
*/
protected void notifyHealthCheckResult(boolean result) {
protected void notifyHealthCheckResult(boolean result, HealthCheckCategoryId category) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wouldn't change the signature (API) of this method in a minor build. Move this signature change to 25/2

}
}

private static final class Empty implements IHealthCheckCategory {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This class is not available as bean as it is marked "private static final". I think this is the intended behavior, maybe add a javadoc indicating that this is just a sentinel value and not a real category available for health checking.

@work-lto work-lto force-pushed the features/lto/23.2/419786_healthcheck branch from db10a07 to b710404 Compare May 12, 2025 10:30
@work-lto work-lto force-pushed the features/lto/23.2/419786_healthcheck branch from b710404 to c7efe91 Compare May 12, 2025 10:33
6439
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants
0