Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 Enclave block and Batch health checks #1727
Add Enclave block and Batch health checks #1727
Changes from 3 commits
09e1415
76554e7
56315ea
15dd266
eee5176
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
The implementation of the
HealthCheck
method has been updated to include checks forl1BlockProcessor
andregistry
. Ensure that the error handling and logging are consistent and that the method's behavior aligns with the intended health check logic.Consider enhancing the error handling to provide more detailed information about which component failed the health check. Additionally, the log level for health check failures should be more severe than
Info
, such asWarn
orError
, to reflect the critical nature of health check failures.Committable suggestion
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.
The
HealthCheck
method has been updated to include additional health checks forl1BlockProcessor
andregistry
. Ensure that the error handling and logging are consistent and that the method's behavior aligns with the intended health check logic.Consider enhancing the error handling to provide more detailed information about which component failed the health check. Additionally, the log level for health check failures should be more severe than
Info
, such asWarn
orError
, to reflect the critical nature of health check failures.Committable suggestion
The
HealthCheck
method has been updated to include additional health checks forl1BlockProcessor
andregistry
. Ensure that the error handling and logging are consistent and that the method's behavior aligns with the intended health check logic.Consider enhancing the error handling to provide more detailed information about which component failed the health check. Additionally, the log level for health check failures should be more severe than
Info
, such asWarn
orError
, to reflect the critical nature of health check failures.Committable suggestion
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.
The
HealthCheck
method inmockBatchRegistry
is not implemented and will cause a panic if called. Consider implementing the method or updating the TODO comment with more details about the intended implementation.Committable suggestion
Check failure on line 7 in integration/simulation/simulation.go
GitHub Actions / lint
Check failure on line 10 in integration/simulation/simulation.go
GitHub Actions / lint
Check failure on line 11 in integration/simulation/simulation.go
GitHub Actions / lint
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.
The implementation of the retry mechanism in
checkHealthStatus
uses a timeout strategy, which is a good practice for network-related operations that might occasionally fail. However, ensure that the panic does not cause the entire application to crash in a production environment. It might be more appropriate to handle the error gracefully and log it for further investigation.Committable suggestion