-
Notifications
You must be signed in to change notification settings - Fork 804
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
"e.map is not a function" JS exception in the UI #1839
Comments
PR to fix this is welcome. |
Hello, I've spent some time looking into this issue and have some conclusions. I've reproduced this issue
This line configures the HealthCheck URL. So when you call /health you get a Health Check Result, also a ResponseWriter is specificed so it's formatted as nice JSON. All good.
This line configures HealthCheckUI back-end URL. This is the back-end URL front-end is polling to get summary of all Health Checks displayed by the UI. In this scenario, there is only one Health Check but there could be more. That's why the expected response is an array of HealthCheck results. Please see the comparison of Health Check response vs Health Check UI back-end response {
"status": "Healthy",
"totalDuration": "00:00:00.0018501",
"entries": { /* ... */ }
} [
{
"id": 1,
"status": "Healthy",
"onStateFrom": "2023-07-26T10:37:56.660717+02:00",
/* ... */
}
] In the setup provided in the issue, identical URL is used as both Health Check URL and Health Check UI back-end URL which is incorrect. Health Check UI back-end is iterating over all configured Health Checks and combines them in a single response (with multiple Health Check Results). The issue can be mitigated by using any different Health Check UI back-end URL. For example:
Could you try this solution @zorgoz? I don't think it's a bug in this package, but you can prove me wrong 😄 . cc @sungam3r |
Sorry, almost all UI stuff is out of my scope for now. So far I am not ready to discuss this area. |
Hi again @zorgoz, Any chance you could have a look if the provided answer/solution works for you? Thanks 👍🏽 |
ping @zorgoz |
1 similar comment
ping @zorgoz |
Similar issue: #661
UI version: 7.0.0-rc2.7
I am encountering following exception, resulting in the UI being totally empty:
Setup is:
/health
response:{"status":"Healthy","totalDuration":"00:00:00.0695283","entries":{"NrgContext":{"data":{},"duration":"00:00:00.0270006","status":"Healthy","tags":[]}}}
(it is fetched by the UI, according to the network tab)
The text was updated successfully, but these errors were encountered: