You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This was first discovered on Black Pacifica during preparation for HASS demo on 06/11/2024 (https://usdot-carma.atlassian.net/browse/CAR-6037).
After starting carma and web ui, the route selection doesn't go through immediately. It looks like the web-ui is not even responding. It takes restart of the web-ui and more than 15s+ waiting for it to actuall get registered.
Due to its inconvenience, I had to use command line scripts to route select and engage which works fine.
interestingly, fusion doesn't have this problem but also I seen this issue on my local VM when I ran carma-config:carma-system-4.5.0-development version.
I also see this error, which I am not sure if it is related.
This makes me wonder if there is a common configuration between the two carma-config or the two environments that is causing this significant delay.
Version
4.5.0 (Current)
Expected Behavior
web-ui should respond immediately.
Actual Behavior
see above.
Steps to Reproduce the Actual Behavior
carma start all on BP
start web-ui on incognito
And select route to see it just delay
Related Work
No response
The text was updated successfully, but these errors were encountered:
Summary
This was first discovered on Black Pacifica during preparation for HASS demo on 06/11/2024 (https://usdot-carma.atlassian.net/browse/CAR-6037).
After starting carma and web ui, the route selection doesn't go through immediately. It looks like the web-ui is not even responding. It takes restart of the web-ui and more than 15s+ waiting for it to actuall get registered.
Due to its inconvenience, I had to use command line scripts to route select and engage which works fine.
interestingly, fusion doesn't have this problem but also I seen this issue on my local VM when I ran carma-config:carma-system-4.5.0-development version.
I also see this error, which I am not sure if it is related.
This makes me wonder if there is a common configuration between the two carma-config or the two environments that is causing this significant delay.
Version
4.5.0 (Current)
Expected Behavior
web-ui should respond immediately.
Actual Behavior
see above.
Steps to Reproduce the Actual Behavior
carma start all on BP
start web-ui on incognito
And select route to see it just delay
Related Work
No response
The text was updated successfully, but these errors were encountered: