Fixes #262: Missing or duplicated results for .filter() when threading is enabled #263
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.
As mentioned in #262, we sometimes see missing or duplicated results when calling nb.dcim.devices.filter() with threading enabled.
Troubleshooting showed that the requests themselves are scheduled with correct offsets, though when the actual calls happen, params seem to be overwritten, further causing incorrect results. Not always, but often enough, and especially visible with low MAX_PAGE_SIZE values.
In the implementation of query.py, I've noticed that concurrent sessions seem to use the same copy of the attrubute "self.filters" (that params = self.filters). That's why params.update(add_params) would sometimes cause collisions depending on the time when a particular request is called.
An example of this dict:
I think changing it to:
will help to mitigate the issue. At least, in my tests it seems to work.
UPD: a bit rewritten my text to make it clearer.