Mathias Fredriksson

I believe this issue is caused by `async_flush_jobs` and might be related to https://github.com/sindresorhus/pure/issues/455. My guess is that there are certain cases where the worker can't handle the `kill -HUP...

Hi @mjrafferty, thanks for reporting. Could you explain how async is being used in the apollo theme? I took a quick look at the code but things are split up...

Btw, what version of Zsh are you using on the rpi?

Hmm, that's interesting. I have two suggestions: 1. Could you test if it's reproducible with only https://github.com/mafredri/zsh-async/commit/32548d3c3f1361de57f09ab9293c902b78f49b55 which excludes the two latter commits that are part of `1.8.0`? 2. On...

Thanks for digging @mjrafferty, I can't seem to reproduce this so it helps. There's only one change I can think of that would affect this behavior, I've reverted it in...

Interesting find! This is definitely not the first time we've had to deal with racy behavior of zptys and it's hard to figure out why they happen. The zpty implementation...

@mjrafferty I may have a fix for this in #45, if you still have a way to test this, it'd be very much appreciated. What I'm thinking, specifically, could affect...

Thanks for reporting. I find it strange that https://github.com/mafredri/zsh-async/commit/361dc171e65c82f57ad814ebecea91c98a6d4b68 is the root cause. It's a commit that doesn't really touch on any worker logic, only modifies the startup procedure a...

> Using my second code snippet the async error code is `2` so something is going on with ZLE. This error originates from: https://github.com/mafredri/zsh-async/blob/490167c4aa5a870b3da1458859bcf3a9d1e24f97/async.zsh#L360 I have never actually ran into...

Ok, this definitely looks like an issue I've been combating since day one. Zpty destroy signals (i.e. HUP) is propagated to all `zpty`s that we're created before the one being...