Quick and dirty bandaid fix to some server crashes which occur to me lately.
The underlying issue seems to be a race condition somewhere when the shell in the pane
exits and the tty file descriptor becomes invalid, but zellij wants to write/read it?
Bug trigger:
- open some panes
- exit the shells in the panes by spamming Ctrl-D
works best when the system only runs on a single CPU, run the following to disable all
cores but one:
echo 0 | sudo tee /sys/devices/system/cpu/cpu*/online
Co-authored-by: raphTec <git@raphtec.net>
* feat(ui): change from non-working alt-brackets to alt-arrows
* style(fmt): rustfmt
* fix: improve parsing of `alt` combination keys
The binding of the keys can now be specified with:
- Alt: 'c'
- Alt: Up
- Alt: Down
- Alt: Left
- Alt: Right
* chore(fmt): rustfmt
Co-authored-by: a-kenji <aks.kenji@protonmail.com>
* fix(screen): handle various edge cases rather than crashing
* style(fmt): rustfmt
* fix(logging): add error logs when unable to find tab
* style(fmt): rustfmt
* feat(ui): round frame corners
* Allow rounded_corners to be set without a palette
* Revert "Allow rounded_corners to be set without a palette"
This reverts commit 9271a4b545.
* fix(style): remove redundant code
* fix(style): clippy lints that somehow got missed
* feat(config): add ui config section
* feature: update rust-toolchain
* add(ci): action that updates `rust-toolchain`
We purposefully keep our version a little behind the newest releases,
to give people the time to update. Now this is unambigious and we can
use all the features our current toolchain allows.
* add(ci): install `cargo-make` through `nix`
Should speed the e2e tests up by about 2 minutes.
Can easily reverted by `commenting/uncommenting`
the `run` part of the `Install cargo-make` step.
* check if cachix speeds the process up
fix(wasm_vm): use `cache_dirs` for ephemeral plugin data
Use proper `cache_directories` by default, that users can be expected
to have proper write permissions for.
The directory is used for plugin hashes, and compilation data.
* fix(feat): `disable_automatic_asset_installation`
This fixes a regression in the feature system:
The asset installation didn't get turned off by the feature.
Add error logging to the install functions.
Properly show features in setup
disable `mkdir` in `wasm_vm` on `feature-disable-asset-installation`
Alternative:
Is this even needed? We make sure the directory is there upon the
normal asset installation.
fixes#1130
