# Upgrade alacritty_terminal in hopes to avoid PTY poll failing · gitcafe/zed

[View on GitCafe](https://git.cafe/gitcafe/zed/commit/c4cf5f2b2c5ebcace1c6647956f6f4fd4459c3cf)

Repository: [gitcafe/zed](https://git.cafe/gitcafe/zed)

Visibility: public

Requested revision: c4cf5f2b2c5ebcace1c6647956f6f4fd4459c3cf

Requested commit: c4cf5f2b2c5ebcace1c6647956f6f4fd4459c3cf

Commit: c4cf5f2b2c5ebcace1c6647956f6f4fd4459c3cf

Tree: d75bdba390161eaa544ba1824613263824d723e7

Author: Thorsten Ball

Committer: Thorsten Ball

## Message

```
Upgrade alacritty_terminal in hopes to avoid PTY poll failing

We saw stack traces in our #panic channel pop up that failed on this line:

    https://github.com/zed-industries/alacritty/blob/33306142195b354ef3485ca2b1d8a85dfc6605ca/alacritty_terminal/src/event_loop.rs#L323-L324

With this message:

    thread 'PTY reader' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 9, kind: Uncategorized, message: "Bad file descriptor" }'
    /Users/administrator/.cargo/git/checkouts/alacritty-afea874b09a502a5/3330614/alacritty_terminal/src/event_loop.rs:324

We don't know how to reproduce the error. It doesn't seem related to the number of open PTY handles,
because `openpty` itself didn't fail. We can only assume that something went wrong between
`openpty` and the setup of the polling.

Since Alacritty itself changed its polling mechanism significantly by switching
from `mio` to `polling` (https://github.com/alacritty/alacritty/pull/6846) we upgraded
with the hope that this will fix the bug.

Co-authored-by: Antonio <antonio@zed.dev>
Co-authored-by: Federico <code@fdionisi.me>
Co-authored-by: David <dammerung2718@icloud.com>
Co-authored-by: Bennet <bennetbo@gmx.de>

```

## Parents

- [f7a2118b159ac98a4fda8f15974090781522b407](https://git.cafe/gitcafe/zed/commit/f7a2118b159ac98a4fda8f15974090781522b407?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zed/tree/c4cf5f2b2c5ebcace1c6647956f6f4fd4459c3cf?format=markdown)