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.
@brettviren I found that, in the function
Aux::untagged_traces()
, thestd::set_difference
was given astd::unordered_set
. However, the elements are actually assumed to be sorted in the std according to cppreference.Here is a quick test:
Note that
untagged_traces
is used inDrifter
,ChannelSelector
,ManifySInk
andFrameMerger
. Given that most of our use cases are just retrieving all traces when the upstream simulation/data has no tag for traces. Therefore, this bug should not make an actual difference.It makes a difference only when the upstream frame does have tagged traces, but we still want to retrieve some untagged traces. As an example in the above test, we have traces 0,1,2,3 and all of them are tagged. If we implement it properly, there should be no untagged traces, but the bug would give us untagged traces 0,1,2,3.