Always log the primary component last so it is joined properly #1217
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.
When investigating #1215 I discovered that even though I was specifying a radius, it was not being applied to the very first points.
The way range-queries work they always start with an element containing all the data based on the latest time the primary key was logged. Since we log the splat after the point, any splatted data was missing from this context and the initial set of points was logged with auto.
Then, I think a point-cloud heuristic was shrinking auto as more points got added to the scene?
Logging the primary component last seems like a generally safe thing to do and will make the range-queries behave properly for now. I also opened #1218 for longer-term work.
Visible history on, and points showing the correctly logged radii:
Checklist
CHANGELOG.md
(if this is a big enough change to warrant it)