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
In order to ensure asynchronous operation of user workflows, coroutines are implemented in the SDK, which use promises. It is a standard situation when we reject them with internal exceptions, which in some branches may not be handled.
However, in the paradigm of react/promise v3, this is considered undesirable practice. Therefore, when a rejected promise is completed, in which there is no exception handler, the error_log() function is called with the error text.
The side effects of such behavior are unpredictable, and it is currently impossible to disable it.
The issue about unhandled exceptions may be fixed once react/promise has the ability to set a permanent handler, not a one-time one.
Thanks to the tests in roadrunner-temporal, other deviations from the normal operation of the SDK were detected. These tests have been partially transferred to the SDK (see #359).
Therefore, I suggest temporarily abandoning react/promise in version 2.6.1 until an solution is found.
The text was updated successfully, but these errors were encountered:
In order to ensure asynchronous operation of user workflows, coroutines are implemented in the SDK, which use promises. It is a standard situation when we reject them with internal exceptions, which in some branches may not be handled.
However, in the paradigm of react/promise v3, this is considered undesirable practice. Therefore, when a rejected promise is completed, in which there is no exception handler, the
error_log()
function is called with the error text.The side effects of such behavior are unpredictable, and it is currently impossible to disable it.
The issue about unhandled exceptions may be fixed once react/promise has the ability to set a permanent handler, not a one-time one.
Thanks to the tests in roadrunner-temporal, other deviations from the normal operation of the SDK were detected. These tests have been partially transferred to the SDK (see #359).
Therefore, I suggest temporarily abandoning react/promise in version 2.6.1 until an solution is found.
The text was updated successfully, but these errors were encountered: