-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Revert "[workspace] Upgrade usockets and uwebsockets" #18289
Conversation
Given the intricacies of testing this problem, it's a bit difficult to know for sure that this is the offending commit but anyway reverting it is no great loss. The purpose of the upgrade was to suss out problems with upstream versions earlier rather than later, which it seems like this has accomplished. We'll re-use #17910 to track the upgrade (and possible incompatibility). |
Since this problem just surfaced again, due to #18516, let me describe here an acceptance test: Using the drake tutorials on Deepnote, running the first two cells of the |
The upgrade in RobotLocomotion#18516 broke meshcat on Deepnote again. See RobotLocomotion#18289.
The upgrade in RobotLocomotion#18516 broke meshcat on Deepnote again. See RobotLocomotion#18289.
The upgrade in RobotLocomotion#18516 broke meshcat on Deepnote again. See RobotLocomotion#18289.
The upgrade in RobotLocomotion#18516 broke meshcat on Deepnote again. See RobotLocomotion#18289.
Reverts #18259. Re-opens #17910.
We have some evidence that a Docker image using this commit will not work with the Nginx proxy server we use for our Deepnote tutorials, yielding a "Bad Gateway" error message instead.
This change is