Skip to content
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

chore: fix ruff warnings #3010

Merged
merged 5 commits into from
Feb 7, 2024
Merged

chore: fix ruff warnings #3010

merged 5 commits into from
Feb 7, 2024

Conversation

agoose77
Copy link
Collaborator

@agoose77 agoose77 commented Feb 7, 2024

This PR fixes some ruff warnings that have appeared. Some are general, some are NumPy.

@agoose77 agoose77 changed the title agoose77/fix ruff warnings chore: fix ruff warnings Feb 7, 2024
@agoose77 agoose77 enabled auto-merge (squash) February 7, 2024 09:52
@agoose77
Copy link
Collaborator Author

agoose77 commented Feb 7, 2024

@ManasviGoyal this should hopefully appease ruff :)

@agoose77 agoose77 merged commit 9096a7c into main Feb 7, 2024
37 of 38 checks passed
@agoose77 agoose77 deleted the agoose77/fix-ruff-warnings branch February 7, 2024 10:12
@agoose77
Copy link
Collaborator Author

agoose77 commented Feb 7, 2024

@jpivarski I set this to automerge, and it succeeded despite the pypy test failure. I assume that means we explicitly don't want this to be a required test?

Have you seen that pypy segfault before? I don't think this PR did anything that would introduce it, so I'm wondering if it's flaky.

@jpivarski
Copy link
Member

It's #2971, a known issue. The reason it's not a required test is because of the segfault. I want to keep running the test, but not require it, to keep in mind that it's an unsolved problem.

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