Open alekspickle opened 1 year ago
Hum, I think this is basically failing to write to STDOUT for some reason... iirc @tlinford encountered something similar recently, right?
yeah, it was in #2329. At least in that case I figure it was just a side effect of the server going down. In the end that error is client side, it shouldn't be related to sessions dying?
Yeah, it's also not even a crash: https://github.com/zellij-org/zellij/blob/6cf795a7df6c83b65a4535b6af0338b4a0b1742f/zellij-client/src/input_handler.rs#L83
I guess these are both symptoms of something else unhandled
Ok, if it's something unhandled unless I find what it is exactly I'll close this
I think it's fine to keep this open as a reported issue, even if we don't yet have enough info how to solve it.
I was trying to check out Graphite with stable diffusion, but when I setup the AI server and try to run it it crashes.
While the fail on the other apps are irrelevant here it somehow also messes up with zellij sessions: first time it detached from the session, and after I reattached and tried to run again it terminated the session. Any idea what would be useful to debug further? Meaningful lines I see in logs are not giving me enough context tbh:
how it looks in the terminal
``` ~ on ☁ (eu-west-2) ➜ zj -s main Session with name "main" already exists. Use attach command to connect to it or specify a different name. ~ on ☁ (eu-west-2) ❯ zj attach main Received empty message from server ~ on ☁ (eu-west-2) took 1m7s ❯ zj attach main No session with the name 'main' found! ```Main question here I suppose - what exit codes can cause such inconsistent behavior?