-
Notifications
You must be signed in to change notification settings - Fork 65
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
Supports passing no providers to FullRepoMetadataConfig. #182
Conversation
Seems reasonable; check pyre and is there any other kind of full repo metadata other than TypeInferenceProvider that we might need to support? |
I don't know why pyre is failing, I cannot get it to repro locally :( I did some digging to try to figure out what the plan was with the I'm going to take a look at fixing that and reconfiguring this to not use placeholders at all if possible. |
Created Instagram/LibCST#475 for the LibCST bug |
Pyre failed due to a type error was found in fixit/rules/cls_in_classmethod.py:286:26 and that's related to the new LibCST release. Line 120 in 1d1cfe9
|
Thanks @jimmylai! No rush, I want to wait on this PR until after Instagram/LibCST#476 is merged and released. I think it will clean up the code here nicely. |
@zsol do you know when LibCST will be released again? I'd like to get this fix in :) Happy to help if I can! |
There has been a new LibCST release so I am back looking at this. The bug in When there is a TimeoutError from using Pyre we trigger this exception that says |
Hey there! We appreciate your contributions, but we're in the process of making some large changes to the core of Fixit. We will try to have more info about the direction we're heading soon, but in the mean time, we are closing all outstanding PR's from before we started this work. Thank you for your understanding. |
Summary
#181
Allowing passing no providers to FullRepoMetadata. There is already a fallback if the provider is broken where a placeholder cache is used, so I used the same codepath to treat empty providers and exceptions the same way.
There is currently only one placeholder cache type so I hardcoded TypeInferenceProvider, but if we want this to be more flexible I can try to build support for multiple.
Test Plan
Added a unit test. Tested manually and exception no longer fires and linters work correctly.