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

The type check of numpy.lib.tests.test_format.$toplevel is taking more than ... (hangs indefinitely) #874

Open
tamird opened this issue Jun 5, 2024 · 0 comments

Comments

@tamird
Copy link

tamird commented Jun 5, 2024

Pyre Bug

Bug description
Running poetry run pyre in my repository hangs.

Reproduction steps
poetry run pyre

Expected behavior
Some output.

Logs
Please include any relevant logs here:

poetry run pyre                                                                                                                                                                                                                                                                (6 results) 12:05:20 [1690/26822]
ƛ No watchman binary found. 
To enable pyre incremental, you can install watchman: https://facebook.github.io/watchman/docs/install
ƛ Defaulting to non-incremental check.
ƛ  Parser error in module `ruyaml.main`: Function signature type comment has 3 parameter types, while the corresponding function contains 5 parameters
ƛ  Parser error in module `lib.common.common.module.industry.message.schema.registry.messages`: CPython runtime raised a non-syntax exception
ƛ  Parser error in module `numpy.core.tests.test_regression`: CPython runtime raised a non-syntax exception
ƛ  Parser error in module `pip._vendor.pyparsing.unicode`: CPython runtime raised a non-syntax exception
ƛ  Parser error in module `pyparsing.unicode`: CPython runtime raised a non-syntax exception                                      
ƛ  The type check of numpy.lib.tests.test_format.$toplevel is taking more than 120 seconds (pid = 17098) [66.5s]

pyre_rage.log

Additional context
Add any other context about the problem here. (like dependencies in your venv, third party stub files being used, overall goals, etc.)

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

No branches or pull requests

1 participant