What happened to Tabby stability/robustness over the past couple of releases?

[ew4adtr]

It seems like what used to be a relatively stable, robust and extremely user friendly tool has dropped in quality significantly with issues that inhibits workflow. The issue with editing a file (vim) in an ssh session hanging Tabby to the point that it needs to be killed via OS task manager / activity manager (cross OS) is a productivity killer. I am curious if I am in the minority, or if these types of issues affect others.

[Eugeny]

Starting with 1.0.216, Tabby has migrated to a new, maintained SSH backend. While it has been available for a long time as an optional beta via the nightly builds, apparently barely anyone has tested it. I've been using it as my daily driver for the last 4 months without issues. Now that it's released, lots of problems are surfacing reported by the dozens of thousands people using tabby in different ways and environments.

I'm currently rushing to fix them and to add support for features (e.g. DH GEX and PPK keys) that were missing in russh compared to mscdex/ssh2. I've spent every evening of my new year's vacation fixing things. Every morning I wake up to an inbox full of github notifications. My new email counter is permanently stuck at 99+ and my only recourse is to fix things incrementally while breaking as little as possible.

The reason the stable, robust and extremely user friendly tool has dropped in quality significantly is that the OSS model is unsustainable by design. It's never going to get better.

You can help by submitting useful bug reports. If you're experiencing a main thread hang like you're describing, capture a perf sample (perf on linux, "sample process" on macOS).

[ew4adtr]

Thanks for your work in maintaining Tabby. I appreciate the magnitude of the change with the introduction of the new SSH backend - the instability this introduced is huge though. Will try to provide perf samples, however I'm not sure how to grab them from Windows, unless you're looking to get these from the connected server.