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
If you open up the dev-tools on the browswer and then look at console, you will see the error:
ERROR Error: duplicate name 'Any' in Namespace .gz.msgs
add namespace.js:240
parseType parse.js:354
parseCommon parse.js:261
parse parse.js:790
onloadend gzweb.module.js:11673
Switching to network and filtering by WebSocket requests, you will see that gzweb sends protos request. (Looking at the gz_launch console log will also show that it has been received). Then the response, when viewed as UTF-8 will see the proto headers sent below. After Wrench message it seems to repeat? Response from gz-garden and gz-harmonic are attached. Note: that the web visualisation works with garden and fortress (as per the steps above)
Before this issue gets solved, what is the best workaround? I need to run gazebo as a websocket server so I can use gzweb2 to render on webpage.
Not sure if this is helpful but my current "workaround" is to just not migrate to harmonic, this is the only thing that is stopping me from migrating from fortress.
Environment
Binary gz-harmonic package from ubuntu-stable
Description
Steps to reproduce
gz sim -v 4 -s -r shapes.sdf
gz launch -v 4 /usr/share/gz/gz-launch7/configs/websocket.gzlaunch
Output
If you open up the dev-tools on the browswer and then look at console, you will see the error:
Switching to network and filtering by WebSocket requests, you will see that gzweb sends protos request. (Looking at the gz_launch console log will also show that it has been received). Then the response, when viewed as UTF-8 will see the proto headers sent below. After Wrench message it seems to repeat? Response from gz-garden and gz-harmonic are attached. Note: that the web visualisation works with garden and fortress (as per the steps above)
gz-garden-response.txt
gz-harmonic-response.txt
Not sure if these duplicate headers are the problem but seems like a bug
The text was updated successfully, but these errors were encountered: