Open
Conversation
Collaborator
Thanks for flagging this! It looks like we messed up something in error filtering in pyrefly 0.58.0 - the errors that we're now failing to report are ones at WARN severity. I'll dig into this tomorrow. (Feel free to merge without waiting for me - I can update again once we release a fixed version.) |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Zuban now passes two more cases (yay!).
Pyrefly also passes two more, but it also regressed on two, around
@deprecatedand Protocol type params. @rchen152 do you know what happened there? Maybe deprecation issues are not enabled in the conformance suite for some reason?