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 the operator implementation expects tasks and flows to be compliant with the specification, otherwise the behavior is undefined.
This happens in the following situations :
programmer mistakes, e.g an operator receives a non-flow where it should be a flow. Not supposed to happen in production but very common during dev time, good reporting could improve user experience.
abnormal conditions such as OutOfMemoryError thrown by a callback. Not supposed to happen in production either, but if/when it does the program should do its best to propagate and report the error.
The text was updated successfully, but these errors were encountered:
Currently the operator implementation expects tasks and flows to be compliant with the specification, otherwise the behavior is undefined.
This happens in the following situations :
OutOfMemoryError
thrown by a callback. Not supposed to happen in production either, but if/when it does the program should do its best to propagate and report the error.The text was updated successfully, but these errors were encountered: