record a middleman action execution . even if middleman are almost instant , we record them because they depend on other actions and we need them for constructing the critical path . for some rules with incorrect configuration transitions we might get notified several times for the same middleman . this should only happen if the actions are shared . concode_field_sep C maxCriticalPath concode_elem_sep Clock clock concode_elem_sep PriorityQueue<C> slowestComponents concode_elem_sep int SLOWEST_COMPONENTS_SIZE concode_elem_sep Object lock concode_elem_sep ConcurrentMap<Artifact,C> outputArtifactToComponent concode_field_sep void actionStarted concode_elem_sep int compare concode_elem_sep void addArtifactDependency concode_elem_sep C tryAddComponent concode_elem_sep void finalizeActionStat concode_elem_sep ImmutableList<C> getSlowestComponents concode_elem_sep C createComponent concode_elem_sep void actionCached concode_elem_sep C getMaxCriticalPath concode_elem_sep A aggregate concode_elem_sep void actionComplete concode_elem_sep boolean isBiggestCriticalPath
void function ( ActionMiddlemanEvent arg0 ) { Action loc0 = arg0 . getAction ( ) ; C loc1 = tryAddComponent ( createComponent ( loc0 , arg0 . getNanoTimeStart ( ) ) ) ; finalizeActionStat ( arg0 . getNanoTimeStart ( ) , loc0 , loc1 ) ; }