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

Send a dummy input to clear the read block #453

Closed
wants to merge 1 commit into from

Conversation

noborus
Copy link
Contributor

@noborus noborus commented Apr 25, 2021

fixed #452.
When switching nonBlocking, a dummy input is sent to process read
and clear the read block.

fixed gdamore#452.
When switching nonBlocking, a dummy input is sent to process read
and clear the read block.
@noborus
Copy link
Contributor Author

noborus commented Apr 25, 2021

There may be other ways to solve this problem. This is an idea.

@codecov
Copy link

codecov bot commented Apr 25, 2021

Codecov Report

❗ No coverage uploaded for pull request base (master@299cb41). Click here to learn what that means.
The diff coverage is 0.00%.

Impacted file tree graph

@@            Coverage Diff            @@
##             master     #453   +/-   ##
=========================================
  Coverage          ?   16.87%           
=========================================
  Files             ?       20           
  Lines             ?     1387           
  Branches          ?        0           
=========================================
  Hits              ?      234           
  Misses            ?     1139           
  Partials          ?       14           
Impacted Files Coverage Δ
nonblock_unix.go 0.00% <0.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 299cb41...88d9bf7. Read the comment docs.

@gdamore
Copy link
Owner

gdamore commented May 15, 2021

This turns out not to be necessary. Please see my "tty" branch for a likely solution.

@gdamore
Copy link
Owner

gdamore commented May 15, 2021

See #459 for my approach that I think sorts this.

@gdamore
Copy link
Owner

gdamore commented May 16, 2021

I've merged #459 into master which addresses this problem, and makes this PR obsolete.

@gdamore gdamore closed this May 16, 2021
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.

Lost a key event once when exiting or suspending in v2.2.1.
2 participants