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
When the reuseV8Context option is enabled, we freeze global objects to prevent modifications from leaking from one Workflow execution context to another one.
However, we do not prevent reassignment of global variables. And since context switching is based solely on global variable names, the engine will leave those reassigned global variable untouched.
Describe the bug
When the
reuseV8Context
option is enabled, we freeze global objects to prevent modifications from leaking from one Workflow execution context to another one.However, we do not prevent reassignment of global variables. And since context switching is based solely on global variable names, the engine will leave those reassigned global variable untouched.
For example, the following test fails:
Deleting a global variable also fails, as the variable "reappears" on the next context switch. For example, the following test fails:
The text was updated successfully, but these errors were encountered: