-
-
Notifications
You must be signed in to change notification settings - Fork 88
Implement Python bindings and stabilize test infrastructure #203 #325
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
Open
gabrielrusanescu
wants to merge
10
commits into
xoriors:main
Choose a base branch
from
gabrielrusanescu:gabrielrusanescu/python-bindings-203
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 8 commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
8ea1c3d
Added Python Bindings for issue 203 (everything that has been done un…
gabrielrusanescu 9f8b98b
Fixed pre-push hooks
gabrielrusanescu f5e2d4a
Fixing pre-push errors
gabrielrusanescu 531c47a
Stabilize test suite and fix concurrency issues
gabrielrusanescu bd31749
Fix memory corruption and concurrency issues by refactoring test reso…
gabrielrusanescu 37d0d76
Fixed mod.rs file
gabrielrusanescu 4661bc4
Added python bindings test to ensure functionality
gabrielrusanescu d3dc9b0
Added variable for compatibility issues
gabrielrusanescu 69aa412
Implemented the solutions from review
gabrielrusanescu fa15108
Added new changes from review comment
gabrielrusanescu File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| [build] | ||
| rustflags = ["--cfg", "rustix_use_libc"] | ||
|
|
||
| [env] | ||
| PYO3_USE_ABI3_FORWARD_COMPATIBILITY = "1" | ||
Oops, something went wrong.
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.
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.
This global
--cfg rustix_use_libcis a build-machine workaround baked into every build of the repo, and it's silently dropped exactly where it matters.Two problems:
Wrong layer. It switches every
rustixin every build — including the production FUSE binary — from thelinux_rawbackend to libc, just to work around the old locked rustix 0.37.28 failing on recent nightly.Cargo.lockstill contains rustix 0.37.28; the PR's owninstructions-python-bindings/fix_rustix_error.mdsays the real fix is updating the locked rustix (cargo update -p rustix, or bumping the dependency that pulls 0.37.x). Doing that makes this cfg unnecessary. (The[workspace.dependencies] rustix = "1.1.4"added in the rootCargo.tomldoesn't help either — no crate references it withworkspace = true, so it pins nothing.)Silently overridden. Cargo ignores
build.rustflagswhenever theRUSTFLAGSenv var is set — andscripts/check-before-push.shline 6 doesexport RUSTFLAGS="-Dwarnings". So the guarded pre-push builds compile without this cfg (hitting the original rustix error on affected toolchains, or silently using a different syscall backend than plaincargo build), and local vs. guarded builds diverge.Suggest: drop this file, update the locked rustix instead, and scope
PYO3_USE_ABI3_FORWARD_COMPATIBILITYto the rencfs-python build (or upgrade pyo3) rather than exporting it repo-wide.Generated by Claude Code