Skip to content

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

Sign in

Sign up

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

PyO3 / pyo3 Public

Notifications You must be signed in to change notification settings
Fork 777
Star 12.6k

Code
Issues 212
Pull requests 66
Discussions
Actions
Projects
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Discussions
Actions
Projects
Security
Insights

CI

fix another `unsafe_op_in_unsafe_fn` trigger (#4753) #12004

Sign in to view logs

Sign in to view logs

fix another `unsafe_op_in_unsafe_fn` trigger (#4753)

fix another `unsafe_op_in_unsafe_fn` trigger (#4753) #12004

Summary
Jobs
Run details
- Usage
- Workflow file

Usage Workflow file

test-cross-compilation ubuntu-latest -> x86_64-unknown-linux-gnu

succeeded Dec 2, 2024 in 1m 9s

Loading

Re-running jobs...

You can’t perform that action at this time.

fix another unsafe_op_in_unsafe_fn trigger (#4753) #12004

test-cross-compilation ubuntu-latest -> x86_64-unknown-linux-gnu

test-cross-compilation ubuntu-latest -> x86_64-unknown-linux-gnu

Re-running jobs...

fix another `unsafe_op_in_unsafe_fn` trigger (#4753) #12004