data: expose downsampling preferences to plugins #3271
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary:
We add a
sampling_hints
attribute to theTBContext
magic container,which is populated with the parsed form of the
--samples_per_plugin
flag. Existing plugins’ generic data modes are updated to read from this
map instead of using hard-coded thresholds.
Test Plan:
This change is not actually observable as is, because the multiplexer
data provider ignores its downsampling argument. But after patching in a
change to make the data provider respect the downsampling argument, this
change has the effect that increasing the
--samples_per_plugin
overthe default (e.g.,
images=20
) now properly increases the number ofsamples shown in generic data mode, whereas previously it had no effect.
wchargin-branch: data-downsampling-flag