Time is not right,the flow is not really finish.
- Dominant language
- Java
- Stars
- 273
- Forks
- 42
- PR merge metrics
- No merged PRs in 30d
Description
Future initTask = threadPool.submit(flowTask);
try {
initTask.get(mTimeout, TimeUnit.MILLISECONDS);
} catch (Exception e) {
LogImpl.w(TAG, "timeout for flow: " + getName());
}
long endTime = System.currentTimeMillis();
LogImpl.i(TAG, getName() + " runs " + (endTime - startTime));
Flow is not really finish.Some task may be still running.
And i think flow or Init need a callback,for example in Android loading Activity.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing the flowTask submission and the initTask.get timeout shown in the issue, then inspect how Init represents flow completion. Define how completion should account for still-running tasks and how a callback would be exposed for an Android loading Activity; done means the flow completion signal and callback behavior are unambiguous.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100