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
It's possible to a code inadvertently (or on purpose) to completely break a running Codelet by using the method getOutput(String type, int index). If someone tries to access an index greater than the size of the outputs, it will change the enable field to false and increment enable_count. As the Codelet tries to run again it will raise an exception, but there is no place where the entity revert to its original state, preventing the Codelet from running indefinitely.
The text was updated successfully, but these errors were encountered:
Wander, I was looking at these old issues not yet dealt with. In this case, I believe it is possible to get the Codelet back on track using the setEnable(true) method. Do you confirm that the problem still persists after you run setEnable(true) ?
It's possible to a code inadvertently (or on purpose) to completely break a running Codelet by using the method getOutput(String type, int index). If someone tries to access an index greater than the size of the outputs, it will change the enable field to false and increment enable_count. As the Codelet tries to run again it will raise an exception, but there is no place where the entity revert to its original state, preventing the Codelet from running indefinitely.
The text was updated successfully, but these errors were encountered: