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

Fix a false positive for Lint/IncompatibleIoSelectWithFiberScheduler #11830

Conversation

koic
Copy link
Member

@koic koic commented Apr 29, 2023

This PR fixes a false positive for Lint/IncompatibleIoSelectWithFiberScheduler when using excepts argument.

AFAIK, IO.wait_readable and IO.wait_writable cannot replace IO objects waiting for exceptions.


Before submitting the PR make sure the following are checked:

  • The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
  • Wrote good commit messages.
  • Commit message starts with [Fix #issue-number] (if the related issue exists).
  • Feature branch is up-to-date with master (if not - rebase it).
  • Squashed related commits together.
  • Added tests.
  • Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
  • Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

This PR fixes a false positive for `Lint/IncompatibleIoSelectWithFiberScheduler`
when using excepts argument.

AFAIK, `IO.wait_readable` and `IO.wait_writable` cannot replace IO objects waiting for exceptions.
@bbatsov bbatsov merged commit 0970cc1 into rubocop:master May 13, 2023
28 checks passed
@bbatsov
Copy link
Collaborator

bbatsov commented May 13, 2023

Thanks!

@koic koic deleted the fix_a_false_positive_for_lint_incompatible_io_select_with_fiber_scheduler branch May 13, 2023 08:17
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.

None yet

2 participants