Fixes wrong result in ListAccessUsers due to loop variable messing with pointers #1482
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.
Description
Changes the variable used for pagination to be inside the loop, and avoid the wrong values in pointers.
4172f09 fixes #1481
Has your change been tested?
Yes, following the steps described in the issue.
I tried to create a test that proves the issue with the pointers (a test that would fail without my changes), but the compiler is force-optimizing all pointers to bool I create into the same one.
I have however a real case to show:
This is my user in ZeroTrust:
This is what the code above above returns (ignoring the other users)
This is what the sniplet above returns (ignoring the other users)
And with my changes:
Types of changes
What sort of change does your code introduce/modify?
Checklist:
and relies on stable APIs.