Open kinsersh opened 9 years ago
I'm experiencing this same issue (with the same ruby and flow versions). Is there a fix coming?
bump...
Given the inactivity on this issue and the GitHub repo in general, we will stop using aws-flow-ruby, instead use the Java equivalent.
Seeing this as well. Is this repo even monitored?
@pmohan6 (I'm picking you out because of the number of commits) who is in charge of this repo?
(Note that I'm no longer associated with AWS, and not at all in charge of this repo. I am willing to fork if necessary, though)
@kinsersh: Sorry to hear that the library failed you :(. If possible, could you post the workflow history/workflow definition that you used when you got that error?(or even better, a small repro case, though they are admittedly obnoxious to write for this library). It definitely does look like an internal error, and it'd be good to fix that (similarly to @DMcKinnon-mdsol and @jcavalieri).
Hi @mjsteger , thanks for helping out. I actually abandoned using this library, so I don't have any readily available samples.
I had a case where an error was raised within my own code that resided within a task, as follows:
The flow framework doesn't properly report on the problem. I instead got this:
I used the replay mechanism to put a breakpoint inside of async_decider to inspect what the failure really was, which ended up being this:
What I want is for aws-flow-ruby to report the problem I raised, properly handling, rather than experiencing what it looks like is internal problems to aws-flow-ruby with error handling. Also, when looking in the SWF console, I only see decision tasks that time out - not very helpful. If the flow framework isn't changed to handle this better, please at least improve the docs.
I have worked around this by defining a rescue block inside each task execution. I am experiencing this problem with ruby 2.2.0 and aws-flow-ruby v3.1.0.