Skip to content

padd: an unreadable sibling does not end the IMU search - #274

Merged
pierre-rouanet merged 1 commit into
pollen-robotics:mainfrom
hadelan:padd-imu-sibling-search
Sep 14, 2026
Merged

padd: an unreadable sibling does not end the IMU search#274
pierre-rouanet merged 1 commit into
pollen-robotics:mainfrom
hadelan:padd-imu-sibling-search

Conversation

@hadelan

@hadelan hadelan commented Sep 12, 2026

Copy link
Copy Markdown
Contributor

imu_sibling walks the event nodes under the pad's HID parent looking for the one with the accelerometer property. One candidate whose device/properties cannot be read — the device was unplugged between the read_dir and the read — returned None for the whole search, and the real IMU sorting after it was never seen: no IMU head control and no monitor panel for the rest of that pad's session.

Skip the vanished candidate and keep walking. Regression test lays out the sysfs tree with a dead sibling between the pad and its IMU. cargo test -p padd, clippy -D warnings, fmt --check all green.

A candidate whose properties read fails — unplugged between the read_dir
and the read, so the file is gone — returned None for the whole search,
and the real IMU sorting after it was never seen: no IMU head control and
a frozen monitor panel for the rest of that pad's session. Skip it and
keep walking.
@pierre-rouanet
pierre-rouanet merged commit 68f984c into pollen-robotics:main Sep 14, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants