Skip to content

CI check for bindings stub files#161

Open
sea-bass wants to merge 11 commits intomainfrom
check-bindings-diff
Open

CI check for bindings stub files#161
sea-bass wants to merge 11 commits intomainfrom
check-bindings-diff

Conversation

@sea-bass
Copy link
Collaborator

@sea-bass sea-bass commented Mar 12, 2026

Adds a check to CI builds to verify nanobind generated stub (.pyi) files.

The check happens with pixi, because all the other CI jobs use Docker and we are not mounting any volumes etc., so checking git diffs doesn't work with how things are now.

Because of this, we now should use pixi run -e ci install_all to ensure we don't use symlink install and we use a consistent version of nanobind managed by the pixi lockfile. Worth it? I think overall it's a positive.

Sorry for the lockfile changes.


Success version:
image

Failing version:
image

@sea-bass sea-bass force-pushed the check-bindings-diff branch from b31e751 to 12adde6 Compare March 12, 2026 01:09
@sea-bass sea-bass force-pushed the check-bindings-diff branch from 6478850 to 84821ef Compare March 12, 2026 01:46
@sea-bass sea-bass requested review from eholum and sjahr March 12, 2026 03:32
@sea-bass sea-bass changed the title CI check for outdated bindings stub files CI check for bindings stub files Mar 12, 2026
Copy link
Collaborator

@eholum eholum left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we use a consistent version of nanobind managed by the pixi lockfile. Worth it?

Hard yes.

# Create a workspace and copy in the source code.
RUN mkdir -p /roboplan_ws
RUN mkdir -p /roboplan_ws \
&& git config --global --add safe.directory /roboplan_ws
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there something running in the images that needs this? If not maybe we should just add a .git/* to the Dockerignore so that it isn't copied into the workspace in the container?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's a much better option.

Basically I went through a few iterations on where to run this CI check, and without these Dockerfile changes running git commands in the containers failed.

But since we're doing it in the Pixi job now...

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