Loukas Agorgianitis

Can be closed when #50 merges

It seems that `jetty-unixsocket` is now deprecated/removed in favor of `jetty-unixdomain-server`: https://github.com/jetty/jetty.project/blob/8aa9c8b01137819415c4517d02138b52a9661218/documentation/jetty/modules/programming-guide/pages/migration/11-to-12.adoc

Usage of the new APIs is documented here: https://jetty.org/docs/jetty/11/programming-guide/server/http.html#connector https://jetty.org/docs/jetty/11/programming-guide/client/http.html#transport-unix-domain

Some more notes: The above problem was reproduced in a linux vm with pci passthrough (vfio). It seems that the problem occurs when both a spice display and the pci...

Keep in mind that this is something I tried for the first time, so I don't know if its a plasma-wayland with multiple video cards (virtio vga/spice + real pci...

Yeah I saw similar mentions to HDR problems with the nvidia 555 driver: https://bbs.archlinux.org/viewtopic.php?id=297236 https://bugs.kde.org/show_bug.cgi?id=488941 https://forums.developer.nvidia.com/t/nvidia-555-52-04-plasma-6-1-wayland-screen-turn-off-on-login/297197 I'm not sure this is the case here though, because I checked in `~/.config/kwinoutputconfig.json`,...

Another discussion that might have relevant info: https://forums.developer.nvidia.com/t/555-release-feedback-discussion/293652/45?page=3

It also seems that launching zsh with `TERM=xterm-256color zsh` from tty does not produce these errors, while leaving the default `TERM=vt220 zsh` does produce them

This is nice, something to mimic `cargo run` from the rust world

Seems that this is caused when cloning repositories over `dumb` http transport instead of `smart` http transport: https://git-scm.com/book/en/v2/Git-Internals-Transfer-Protocols