Jean-Baptiste Barth
Jean-Baptiste Barth
Today simpleflow only logs to stdout and with little contextual information on the performed actions. It falls flat when trying to identify logs from a specific workflow or activity at...
Today we force to have a "workflow" as argument to decider.start, but we should be able to start with just a task list name and find the correct workflow the...
The current format and naming scheme suffers from the following problems: - activities are identified by their name, which are not guaranteed to be unique (names can be reused for...
A few problems I got with history concepts in both swf and simpleflow: - inconsistent timestamp keys for "tasks" other than activities (signals, timers, markers) => see https://github.com/botify-labs/simpleflow/commit/7b30a37c1512ceb09f74f5deece255982412413c#commitcomment-27044383 - simpleflow's...
Today those hooks are executed on the decider after sending the decision to complete/fail the workflow. Having this would fit better with the SWF principles, be easier to tool, to...
@ampelmann noticed that with recent changes on `swf.format` module, the code raises but that may leave tasks running while in fact they are not. This is especially true if we...
The workflow "run()" method receives a "None" as first and only argument (+ self obviously) if no parameter is passed as input, resulting in exceptions like: ``` TypeError: run() takes...
Recently at Botify we hit situations where we would overflow our [SWF rate limits](http://docs.aws.amazon.com/amazonswf/latest/developerguide/swf-dg-limits.html), especially in `RecordActivityTaskHeartbeat` and `PollForActivityTask` operations. The main problem for me is that we hit a...
If task1 fails once, and is retried, you get two activities in the history: one scheduled at event ID "153" for instance, and the retry scheduled at event ID "159"....