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
functions inside expressions are evaluated in coroutine and on panic are not recovered thus crashing whole application. I think there should be somekind of recover as when coroutine ends with not recovered panic the whole application gets shutdown by go runtime.
note: why it is done in coroutine? from timeout or context cancellation perspective this makes little sense because if there is endless loop returning from expression that "timeouted" makes little difference because that endless coroutine still works on background.
The text was updated successfully, but these errors were encountered:
aldas
changed the title
expression are evaluated in coroutine and on panic are not recovered thus crashing whole application
functions inside expression are evaluated in coroutine and on panic are not recovered thus crashing whole application
Mar 9, 2022
Yangruipis
pushed a commit
to Yangruipis/gval
that referenced
this issue
Aug 5, 2022
functions inside expressions are evaluated in coroutine and on panic are not recovered thus crashing whole application. I think there should be somekind of recover as when coroutine ends with not recovered panic the whole application gets shutdown by go runtime.
gval/functions.go
Line 16 in 12d4df2
and
gval/functions.go
Line 39 in 12d4df2
note: why it is done in coroutine? from timeout or context cancellation perspective this makes little sense because if there is endless loop returning from expression that "timeouted" makes little difference because that endless coroutine still works on background.
The text was updated successfully, but these errors were encountered: