-
Notifications
You must be signed in to change notification settings - Fork 17.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Correct handling of more than 256 fence items #28683
Correct handling of more than 256 fence items #28683
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Have you checked for any other callers to max_items? Just wondering if there are downstream users (like Dijkstras) that may not have been exposed to more than 255 fence items
I did grep for I didn't stop to think about avoidance. I just have and it seems to use |
.... Dijkstra does seem to impose a 255 point limit, however. |
a5761d2
to
97e595a
Compare
Found and fixed a fence-transfered-via-FTP bug in here now. We also were not gracefully handling an attempt to upload a fence with >255 vertexes - that's been fixed, too. |
In addition to the new autotests I've done a bunch of tootling around in SITL to make sure fences still generally work. Including Dijkstras with 765 points. |
953a27d
to
7da7ba0
Compare
we allocate RAM based on the size of this structure
this assignments following these lines were silently truncating the param1 value to uint8_t value
7da7ba0
to
b2880ab
Compare
No description provided.