Wenjun Ruan

It‘s better to create a new branch e.g. api-refactor, and don't merge this kind of pr to dev, otherwise, we may need to solve many conflicts before 4.0 @SbloodyS @caishunfeng...

> > It‘s better to create a new branch e.g. api-refactor, and don't merge this kind of pr to dev, otherwise, we may need to solve many conflicts before 4.0...

> > > > It‘s better to create a new branch e.g. api-refactor, and don't merge this kind of pr to dev, otherwise, we may need to solve many conflicts...

Do you have any good idea? AFAIK, we can use xx task SDK to submit task, and can get the appId from SDK, then we don't need to parse from...

> @ruanwenjun Yeh, maybe a practicable solution, we can simply talk about it. > > Before submitting a yarn job, the client apply the application context from RM first, and...

> @ruanwenjun Hi, i wanna ask some maybe dumb question. When worker failover, in the function of `killYarnJob`, the logic is send a view log request to worker and then...

> > already > > > > @ruanwenjun Yeh, maybe a practicable solution, we can simply talk about it. > > > Before submitting a yarn job, the client apply...

We can use a single WorkflowEventQueue, and for each TaskInstance we can create a TaskEventQueue, all state changed are at the event handler. we can control the event handle at...

@wjf222 Please resolve the dependency check failure.

This PR only include front-end code, can it close #11195? I will remove the `close` action.