Closed shireenf-ibm closed 6 months ago
peers in the exposureMap to be excluded from the final result []ExposedPeer
why is this related to the next PR? it cannot be done in this PR?
to handle the case of two different representative peers with same labels
what does this mean? (what was the planned handling?) it should not be possible to generate multiple representative peers with same labels.. consider add caching by labels hash in this PR?
I would prioritize as the next sub task basic tests for exposure analysis results
, before the next optimization task
peers in the exposureMap to be excluded from the final result []ExposedPeer
why is this related to the next PR? it cannot be done in this PR?
to handle the case of two different representative peers with same labels
what does this mean? (what was the planned handling?) it should not be possible to generate multiple representative peers with same labels.. consider add caching by labels hash in this PR?
no further todo's like those related to this PR
236
sub-task :
in this PR:
namespaceSelector
in the policies