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
Currently, all workspaces::sandbox() calls will spin up a new sandbox instance. This was to prevent non-determinism from multiple tests hitting the same node and potentially spinning up similarly sounding accounts and/or modifying similar data with patch state. But this might not be the best for most use-cases and I think we can be less strict about this.
I think we can switch the defaults over to using a single sandbox, and if users are experiencing this non-determinism, they can switch it back over to multiple sandbox. I'm not sure this is the best default, but this is very open to opinions so comment if there's anything that could be worked out better.
Alternatively, we can have an extra macro for each test that points to the port for the sandbox like #<span class="error">[sandbox::at_port(3030)]</span> or #<span class="error">[sandbox::multi_instance]</span>. Or if we don't want to use macros, we can have it be a separate function like workspaces::sandbox_on(3030).
The text was updated successfully, but these errors were encountered:
Currently, all
workspaces::sandbox()
calls will spin up a new sandbox instance. This was to prevent non-determinism from multiple tests hitting the same node and potentially spinning up similarly sounding accounts and/or modifying similar data with patch state. But this might not be the best for most use-cases and I think we can be less strict about this.I think we can switch the defaults over to using a single sandbox, and if users are experiencing this non-determinism, they can switch it back over to multiple sandbox. I'm not sure this is the best default, but this is very open to opinions so comment if there's anything that could be worked out better.
Alternatively, we can have an extra macro for each test that points to the port for the sandbox like
#<span class="error">[sandbox::at_port(3030)]</span>
or#<span class="error">[sandbox::multi_instance]</span>
. Or if we don't want to use macros, we can have it be a separate function likeworkspaces::sandbox_on(3030)
.The text was updated successfully, but these errors were encountered: