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
Rojo still has the problem due to old dependencies
However, rojo still has this problem. While #548 updated the contents of rbx_dom_weak from 2.3.0 to 2.4.0 on June 5th, rbx_binary still is on version 0.6.4, having last been updated on October 11th 2021. I believe it's likely that updating rbx_binary to 0.6.5 will fix this by pulling in the fix PR.
Updating the dependency seems to fix the problem.
On a local development copy, updating the rbx_binary dependency of Rojo to 0.6.5 seems to fix the problem (or at least the error message doesn't show up). I can't get some of the tests running locally though on the base due to timeouts. I think this might just be a problem with my local setup though.
I'm going to further verify the fixes locally. I can submit a PR, otherwise feel free to just bump the version.
The text was updated successfully, but these errors were encountered:
tl;dr I think we can fix this issue by updating rbx_binary from 0.6.4 to 0.6.5.
The problem
I noticed that when saving a package in a Place using remodel, it saves fine but when building the place with rojo, it runs into an error:
rbx_binary fixed this back in April
FilamentGames fixed this back in April for rbx_binary with this PR. That was pulled into remodel by a commit updating remodel dependencies on June 13th in v0.10.0. Remodel now doesn't have this problem.
Rojo still has the problem due to old dependencies
However, rojo still has this problem. While #548 updated the contents of rbx_dom_weak from 2.3.0 to 2.4.0 on June 5th, rbx_binary still is on version 0.6.4, having last been updated on October 11th 2021. I believe it's likely that updating rbx_binary to 0.6.5 will fix this by pulling in the fix PR.
Updating the dependency seems to fix the problem.
On a local development copy, updating the rbx_binary dependency of Rojo to 0.6.5 seems to fix the problem (or at least the error message doesn't show up). I can't get some of the tests running locally though on the base due to timeouts. I think this might just be a problem with my local setup though.
I'm going to further verify the fixes locally. I can submit a PR, otherwise feel free to just bump the version.
The text was updated successfully, but these errors were encountered: