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
We should avoid working with the goja runtime from within the business logic (i.e. outside the mapping layer), because we could be running such code from off the main goja thread (a new goroutine or promise) and when multiple goroutines try to work with the goja runtime at the same time it can cause (avoidable) panics.
The content you are editing has changed. Please copy your edits and refresh the page.
What
Move the usage of goja runtime out of remote_object.go.
Why
We should avoid working with the goja runtime from within the business logic (i.e. outside the mapping layer), because we could be running such code from off the main goja thread (a new goroutine or promise) and when multiple goroutines try to work with the goja runtime at the same time it can cause (avoidable) panics.
Tasks
The text was updated successfully, but these errors were encountered: