Fridolín Pokorný
Fridolín Pokorný
This looks like an issue on Celery side when deserializing exception. It will be good to take a look if the given exception was raised when task fails or succeeds....
Note that this needs to be disjoint from `fallback: true` in the YAML configuration.
The implementation is ready in Selinonlib, it needs changes in Selinon itself though.
This is already implemented, there is a need to update docs though as it is not stated there.
As of now, the fallback node is run always with `parent=None`: https://github.com/selinon/selinon/blob/33dede9d3bee667365279b4f6b0101c3e6c88fd3/selinon/system_state.py#L526-L528
The logic for retrieving exception is already present: https://github.com/selinon/selinon/blob/master/selinon/selinon_task.py#L108-L125 I think I forgot to implement the parent propagation functionality.
> Thanks for your responses. My team is debating forking this project to make it meet our needs. We see you haven't developed on this in a while. What is...
This might be confusing in many cases since flows can have multiple tasks of a same type. A solution would be to include flags: - `any` - similar to Python's...
> We understand Selinon Config class is not Singleton and Celery is loading the Class and missing the Dispatcher Queue configuration which set in the main process which initiated in...
Hi Rathish, I haven't spotted anything suspicious in the provided example (is ``flow_definition`` variable unused intentionally?). There looks like to be an issue with initialization of Selinon - the configuration...