Fix edge condition on Boost fix versions - #425
Merged
Merged
Conversation
… the bug. Make sure that verison is included.
svwilliams
force-pushed
the
fix-boost-1.90-any-range-bug2
branch
from
May 5, 2026 15:28
bc0857f to
7dfdec2
Compare
svwilliams
added a commit
that referenced
this pull request
Jun 6, 2026
Boost Version 1.90 is affected by the any_range bug. Make sure that version is included in the fix.
svwilliams
added a commit
that referenced
this pull request
Jun 6, 2026
Boost Version 1.90 is affected by the any_range bug. Make sure that version is included in the fix.
ikhann
added a commit
to ikhann/fuse
that referenced
this pull request
Aug 15, 2026
Revives the CI effort from locusrobotics#346, which was approved but stalled on a Ceres installation failure in 2023. Building inside the ros:<distro> container images avoids that class of problem entirely: the matching Ubuntu base and ROS apt sources come with the image, and rosdep resolves libceres-dev without additional setup. The workflow builds and tests every package except fuse_viz (blocked on Qt6 support, see locusrobotics#421) and fuse_doc (rosdoc2 configuration only). A weekly scheduled run catches breakage caused by upstream changes (new Boost, Ceres, or rclcpp releases) even when the repository is quiet - the failure modes of locusrobotics#396 and locusrobotics#423/locusrobotics#424/locusrobotics#425. A second job runs the google-benchmark suites in Release mode and uploads the results as an artifact. As a side effect this fixes the CodeQL "Analyze (actions)" check that currently fails on every pull request: the actions language analysis errors out with "CodeQL could not process any code written in GitHub Actions" because these branches contain no workflow files to scan. The devcontainer provides the same ros:rolling environment for local development, with rosdep dependency installation on create.
ikhann
added a commit
to ikhann/fuse
that referenced
this pull request
Aug 16, 2026
Revives the CI effort from locusrobotics#346, which was approved but stalled on a Ceres installation failure in 2023. Building inside the ros:<distro> container images avoids that class of problem entirely: the matching Ubuntu base and ROS apt sources come with the image, and rosdep resolves libceres-dev without additional setup. The workflow builds and tests every package except fuse_viz (blocked on Qt6 support, see locusrobotics#421) and fuse_doc (rosdoc2 configuration only). A weekly scheduled run catches breakage caused by upstream changes (new Boost, Ceres, or rclcpp releases) even when the repository is quiet - the failure modes of locusrobotics#396 and locusrobotics#423/locusrobotics#424/locusrobotics#425. A second job runs the google-benchmark suites in Release mode and uploads the results as an artifact. As a side effect this fixes the CodeQL "Analyze (actions)" check that currently fails on every pull request: the actions language analysis errors out with "CodeQL could not process any code written in GitHub Actions" because these branches contain no workflow files to scan. The devcontainer provides the same ros:rolling environment for local development, with rosdep dependency installation on create.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fix edge condition on Boost fix versions. Version 1.90 is affected. Switch from < 109000 to < 109100.