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.
|
8/31/2018 5:55:47 PM
release in CI environment.
|
8/30/2018 7:43:58 PM
3.54.0
jobtype for reportal. User is able to run presto query through reportal UI with a shared presto account defined in jobtype plugin config. Presto account password could be encrypted and kept in the config file, and it requires a key path file which could be defined in jobtype plugin config to decrypt.
|
8/30/2018 4:02:31 PM
deploy latest master to our staging cluster. The observation of this bug is all execution history table is missing.

The cause looks like a javascript or backbone grammar issue.
The fix is quite simple.
|
8/27/2018 2:23:16 PM
3.52.03.53.0
workflow - validate conditions
* Address comments
|
