Closed EricCousineau-TRI closed 5 years ago
@jamiesnape Now that this is updated, should we update the fork?
Indeed. There are a whole host of other SHA bumps in PR at the moment, so makes sense.
You may want to catch #10575 before it merges.
I considered that, but it's already passed all CI. Since you'll need a macOS CI spin anyway for this bump, we might as well do that in a new PR.
(I could still roll it into #10576 or #10578 though, if you want to wait on those being ready.)
I think a separate PR is fine. I thought #10575 was updating it already to a different SHA, but that was meshcat
, not meshcat_python
.
From this test (the top-level bit): https://drake-cdash.csail.mit.edu/testDetails.php?test=25858064&build=1110775
Reproducible via: