Dong H. Ahn
Dong H. Ahn
Turns out I can also fix this issue if I don't have bidirectional edges (`in` and `contains`). Apparent if `cluster0->rack0->storage_unit0` is mark down, all of the vertices under it should...
> Higher-level question, this is mainly an aesthetic thing, right For now yes because we only do resource type based matching. But at some point, we will introduce name-based matching...
@cmoussa1: same comments. probably good time to start making for this item from flux-sched.
> In the propagate method introduced in #665, the only way to follow the ancestry of a resource vertex to the root of a hierarchy is by manipulating the path...
> I just realized that if we are going to rely on these edges in propagate, then adding them back in can't be optional. We can use @milroy's current technique...
You should be able to give a higher number if the resource vertex doesn't have an allocation. Maybe you can use a large constant number if the vertex is free...
>until after ~17 years, :-) Uptime of 17 years .... Sounds good on more studies
From @SumedhArani: I've been going through the source code of reporting routine of tsan and what @dongahn suggests can be certainly done and does add a benefit of doing a...
From @dongahn: Sounds like progress! This sounds right. I think a key is to make this a callback architecture. One can have a default function as you described which does...
From @SumedhArani: @dongahn Could you please elaborate as I didn't understand clearly > But some ppl may want to have a bit finer granularity differentating the code location that came...