-
-
Notifications
You must be signed in to change notification settings - Fork 786
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
add Fedora/Centos support to get-deps #10
Merged
Merged
Conversation
This file contains 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
Codecov Report
@@ Coverage Diff @@
## master #10 +/- ##
=======================================
Coverage 85.93% 85.93%
=======================================
Files 15 15
Lines 2261 2261
=======================================
Hits 1943 1943
Misses 318 318 Continue to review full report at Codecov.
|
Thanks! |
quark-zju
added a commit
to quark-zju/wezterm
that referenced
this pull request
Jan 6, 2020
I was running `hg log --config pager.pager=sp` and pressing space without releasing it. After about 10k lines sp appears to deadlock. It seems sp uses a single thread for both reading terminal events and sending wake events and it sends too many wake events without reading the events. Failing to write to the wake pipe due to EWOULDBLOCK does not seem to be a problem - there are enough events in the pipe to wake up the other side. Therefore let's just make wake_pipe_write nonblocking and treat EWOULDBLOCK as a success. Context: The stuck thread looks like: #0 0x00007f32671ee237 in write () from /usr/lib/libc.so.6 wez#1 0x000055c466022823 in std::sys::unix::fd::FileDesc::write () at src/libstd/sys/unix/fd.rs:96 wez#2 std::sys::unix::net::Socket::write () at src/libstd/sys/unix/net.rs:276 wez#3 <&std::sys::unix::ext::net::UnixStream as std::io::Write>::write () at src/libstd/sys/unix/ext/net.rs:597 wez#4 <std::sys::unix::ext::net::UnixStream as std::io::Write>::write () at src/libstd/sys/unix/ext/net.rs:582 wez#5 0x000055c465d010a6 in termwiz::terminal::unix::UnixTerminalWaker::wake (self=0x7ffe6bd32de0) at /home/quark/.cargo/git/checkouts/wezterm-6425bab852909cc8/ef1b836/termwiz/src/terminal/unix.rs:278 wez#6 0x000055c465a6c64b in streampager::event::EventSender::send_unique (self=0x7ffe6bd32dd0, event=..., unique=0x7ffe6bd32de8) at src/event.rs:66 wez#7 0x000055c465a7e65a in streampager::display::start (term=..., term_caps=..., events=..., files=..., error_files=..., progress=..., mode=streampager::config::FullScreenMode::Auto) at src/display.rs:295 wez#8 0x000055c465a453a7 in streampager::Pager::run (self=...) at src/lib.rs:171 wez#9 0x000055c465a0aced in sp::open_files (args=...) at src/bin/sp/main.rs:170 wez#10 0x000055c465a08e4f in sp::main () at src/bin/sp/main.rs:25
wez
pushed a commit
that referenced
this pull request
Jan 6, 2020
I was running `hg log --config pager.pager=sp` and pressing space without releasing it. After about 10k lines sp appears to deadlock. It seems sp uses a single thread for both reading terminal events and sending wake events and it sends too many wake events without reading the events. Failing to write to the wake pipe due to EWOULDBLOCK does not seem to be a problem - there are enough events in the pipe to wake up the other side. Therefore let's just make wake_pipe_write nonblocking and treat EWOULDBLOCK as a success. Context: The stuck thread looks like: #0 0x00007f32671ee237 in write () from /usr/lib/libc.so.6 #1 0x000055c466022823 in std::sys::unix::fd::FileDesc::write () at src/libstd/sys/unix/fd.rs:96 #2 std::sys::unix::net::Socket::write () at src/libstd/sys/unix/net.rs:276 #3 <&std::sys::unix::ext::net::UnixStream as std::io::Write>::write () at src/libstd/sys/unix/ext/net.rs:597 #4 <std::sys::unix::ext::net::UnixStream as std::io::Write>::write () at src/libstd/sys/unix/ext/net.rs:582 #5 0x000055c465d010a6 in termwiz::terminal::unix::UnixTerminalWaker::wake (self=0x7ffe6bd32de0) at /home/quark/.cargo/git/checkouts/wezterm-6425bab852909cc8/ef1b836/termwiz/src/terminal/unix.rs:278 #6 0x000055c465a6c64b in streampager::event::EventSender::send_unique (self=0x7ffe6bd32dd0, event=..., unique=0x7ffe6bd32de8) at src/event.rs:66 #7 0x000055c465a7e65a in streampager::display::start (term=..., term_caps=..., events=..., files=..., error_files=..., progress=..., mode=streampager::config::FullScreenMode::Auto) at src/display.rs:295 #8 0x000055c465a453a7 in streampager::Pager::run (self=...) at src/lib.rs:171 #9 0x000055c465a0aced in sp::open_files (args=...) at src/bin/sp/main.rs:170 #10 0x000055c465a08e4f in sp::main () at src/bin/sp/main.rs:25
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.