Remove AlwaysNullReadOnlyVariableDetector from SlackIssueRegistry#410
Merged
Remove AlwaysNullReadOnlyVariableDetector from SlackIssueRegistry#410
Conversation
ZacSweers
approved these changes
Jul 17, 2025
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.
Summary
We've narrowed down the cause of #400 to
AlwaysNullReadOnlyVariableDetector. We're not entirely sure why this detector is causing the error, but we're going to disable it temporarily to allow the other detectors to be updated as we investigate it further.Fixes #400
Requirements (place an
xin each[ ])