From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>,
Dominik Csapak <d.csapak@proxmox.com>
Subject: [pbs-devel] applied-series: [PATCH xtermjs v3 0/4] rewrite in rust
Date: Thu, 23 Jul 2020 12:29:18 +0200 [thread overview]
Message-ID: <a4949d24-c1eb-6d79-0e14-02d39ad8e6be@proxmox.com> (raw)
In-Reply-To: <20200721090048.28632-1-d.csapak@proxmox.com>
On 21.07.20 11:00, Dominik Csapak wrote:
> this series includes a rewrite of termproxy in rust,
> and some smaller ui improvements
>
> changes from v2:
> * cargo clippy fixes & rustfmt
> * fixed bug with timed out clients (wrong elapsed calculation)
> * only prevent closing from the window when the console is connected
> * added parameter 'port-as-fd' which tells termproxy to interpret
> the port number as open fd for a listening socket where it can
> accept
>
> changes from v1:
> * incoroporate suggestions from wolfgang, thx :)
> * fix a bug where we did not exhaust reads from either side before
> closing, discarding possibly some information
> * include a handlebars template (for pbs)
> * improves ui error handling
> * RFC: prevent accidental closing of terminal window
>
> needs a bump for the proxmox crate (also in the Cargo.toml here)
> also missing a bump and changelog entry
>
> Dominik Csapak (4):
> termproxy: rewrite in rust
> add handlebars template
> ui: improve error message handling
> ui: prevent accidental closing of terminal window
>
> .cargo/config | 5 +
> Cargo.toml | 14 +
> Makefile | 52 +++-
> debian/compat | 1 -
> debian/control | 16 --
> debian/debcargo.toml | 14 +
> debian/install | 1 +
> debian/rules | 8 +-
> debian/source/format | 1 -
> debian/source/lintian-overrides | 4 +-
> src/Makefile | 7 -
> src/PVE/CLI/Makefile | 8 -
> src/PVE/CLI/termproxy.pm | 250 -----------------
> src/PVE/Makefile | 3 -
> src/bin/Makefile | 7 -
> src/bin/termproxy | 8 -
> src/main.rs | 456 ++++++++++++++++++++++++++++++++
> src/www/Makefile | 21 --
> src/www/index.html.hbs.in | 23 ++
> src/www/main.js | 33 ++-
> 20 files changed, 586 insertions(+), 346 deletions(-)
> create mode 100644 .cargo/config
> create mode 100644 Cargo.toml
> delete mode 100644 debian/compat
> delete mode 100644 debian/control
> create mode 100644 debian/debcargo.toml
> create mode 100644 debian/install
> delete mode 100644 debian/source/format
> delete mode 100644 src/Makefile
> delete mode 100644 src/PVE/CLI/Makefile
> delete mode 100644 src/PVE/CLI/termproxy.pm
> delete mode 100644 src/PVE/Makefile
> delete mode 100644 src/bin/Makefile
> delete mode 100755 src/bin/termproxy
> create mode 100644 src/main.rs
> delete mode 100644 src/www/Makefile
> create mode 100644 src/www/index.html.hbs.in
>
applied series, thanks!
prev parent reply other threads:[~2020-07-23 10:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 9:00 [pbs-devel] " Dominik Csapak
2020-07-21 9:00 ` [pbs-devel] [PATCH xtermjs v3 1/4] termproxy: " Dominik Csapak
2020-07-21 9:00 ` [pbs-devel] [PATCH xtermjs v3 2/4] add handlebars template Dominik Csapak
2020-07-21 9:00 ` [pbs-devel] [PATCH xtermjs v3 3/4] ui: improve error message handling Dominik Csapak
2020-07-21 9:00 ` [pbs-devel] [PATCH xtermjs v3 4/4] ui: prevent accidental closing of terminal window Dominik Csapak
2020-07-23 10:29 ` Thomas Lamprecht [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a4949d24-c1eb-6d79-0e14-02d39ad8e6be@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=d.csapak@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox