⚡ jobflow-controller jobtemplate-controller enqueue should use struct not pointer #3134
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.
Why should not use pointer
The workqueue will deduplicate same item in queue.
According the internal struct of workqueue, when we add a item to workqueue firstly, workqueue will also put it in q.dirty which is `map[interface]struct{}``
before this item processed, if same item re added to the workqueue , this add will skiped
the current code use
*apis.FlowRequest
as item to add to the workqueue, even the different apis.FlowRequest have same values, different*apis.FlowRequest
will be considerd as different item in workqueue, so the deduplication is not work.We can try the example code blow,
the
CompareMap
will Printthe
CompareMapB
will Print