Skip to content

[BLD]: fix maturin strip/include-debuginfo conflict - #7640

Open
mayuriphad wants to merge 1 commit into
chroma-core:mainfrom
mayuriphad:fix/maturin-strip-debuginfo-conflict
Open

[BLD]: fix maturin strip/include-debuginfo conflict#7640
mayuriphad wants to merge 1 commit into
chroma-core:mainfrom
mayuriphad:fix/maturin-strip-debuginfo-conflict

Conversation

@mayuriphad

Copy link
Copy Markdown

Summary

maturin dev fails locally with:

Caused by: --include-debuginfo cannot be used with --strip

Root cause: the workspace [profile.release] sets debug = 2 with
split-debuginfo = "unpacked", which makes maturin automatically pass
--include-debuginfo. That collides with strip = true under
[tool.maturin] in pyproject.toml.

Fix: disable strip in [tool.maturin] so it no longer conflicts with the
release profile's own debug-info settings.

Fixes #6536

Test plan

  • maturin dev no longer errors with the strip/include-debuginfo conflict locally
  • CI build/test suite

Local maturin dev builds fail with "--include-debuginfo cannot be
used with --strip" because the workspace [profile.release] sets
debug = 2 with split-debuginfo = "unpacked", which makes maturin
auto-pass --include-debuginfo. That collides with strip = true in
[tool.maturin]. Disable strip there instead, matching the profile's
own intent to keep debug info.

Fixes chroma-core#6536
Copilot AI lite review requested due to automatic review settings August 26, 2026 16:37

@claude claude Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Claude Code Review

This pull request is from a fork — automated review is disabled. A repository maintainer can comment @claude review to run a one-time review.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@github-actions

Copy link
Copy Markdown

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

  • Can you think of any use case in which the code does not behave as intended? Have they been tested?
  • Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
  • If appropriate, are there adequate property based tests?
  • If appropriate, are there adequate unit tests?
  • Should any logging, debugging, tracing information be added or removed?
  • Are error messages user-friendly?
  • Have all documentation changes needed been made?
  • Have all non-obvious changes been commented?

System Compatibility

  • Are there any potential impacts on other parts of the system or backward compatibility?
  • Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

  • Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

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.

[Bug]: Can't build rust bindings locally

2 participants