|
|
9/14/2018 6:58:49 PM
is synchronized, one thread might block all others from entering into this method when it's stuck fetching token. So it's important to prompt users about which step the job is stuck with.
|
9/14/2018 3:26:33 PM
Fix flaky test of runFlowOnJobStatusConditionNull
* Fix flaky test runFlowOnJobStatusConditionNull_2
|
9/13/2018 8:23:24 PM
by using a non-zero wait time when the while loop won't be exited immediately after first wait.
- Reorganize code to improve readability
|
9/13/2018 5:58:12 PM
had a recursion loop like this:
selectExecutorAndDispatchFlow -> handleDispatchExceptionCase -> selectExecutorAndDispatchFlow -> ..
..with max depth of activeExecutors.size()
Iterative approach is easier to reason about, and is totally safe against StackOverflowError.
This is also preliminary refactoring to eventually allow configuring higher max for dispatching errors. Currently, however, max dispatch attempts is capped by the total number of active executors (because each executor is only tried once). In the future I'd like to remove that limit and rely solely on the MAX_DISPATCHING_ERRORS_PERMITTED property.
|
|
|
9/6/2018 6:30:03 PM
Fix flaky test of runFlowOnJobStatusConditionNull
* Disable flaky test: testKillBasicFlowWithoutEndNode
* Address comment.
|
9/6/2018 6:29:08 PM
email instead
Not evicting executions, sending an email instead.
This is to fix #1653 instead of #1654.
* Improved sendFailedUpdateEmail javadoc
* Send unresponsive email less often
* Add TODO comment about possibility of pair == null
|
9/4/2018 3:20:11 PM
3.56.03.57.0
introduced a bug that executions history cannot be displayed in executions tab give every project
The issue is that javascript cannot find ${size}. The resolution is simple that we should add "size" to the context so that javascript is able to locate it.
|
8/31/2018 5:56:04 PM
3.55.0
intention of the original test is to verify if the condition is null, it should take the default value all_success. Modify the test case to make it clear and stable.
|
