From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox 0/9] preparation for websocket api
Date: Wed, 15 Jul 2020 10:15:14 +0200 [thread overview]
Message-ID: <1594800868.gpoilatxdp.astroid@nora.none> (raw)
In-Reply-To: <20200714110957.31884-1-d.csapak@proxmox.com>
$ cargo test
[...]
test src/api/const_regex.rs - const_regex (line 32) ... ok
test src/tools/vec.rs - tools::vec (line 19) ... ok
test src/api/router.rs - api::router::Router (line 216) ... ok
test src/tools/websocket.rs - tools::websocket::FrameHeader::try_from_bytes (line 301) ... FAILED
test src/tools/websocket.rs - tools::websocket::create_frame (line 112) ... FAILED
test src/tools/websocket.rs - tools::websocket::create_frame (line 125) ... FAILED
test src/tools/websocket.rs - tools::websocket::WebSocketWriter (line 182) ... ok
test src/tools/websocket.rs - tools::websocket::create_frame (line 99) ... FAILED
test src/tools/vec/byte_vec.rs - tools::vec::byte_vec (line 4) ... ok
test src/tools/vec/byte_vec.rs - tools::vec::byte_vec::ByteVecExt (line 15) ... ok
test src/tools/vec/byte_vec.rs - tools::vec::byte_vec::ByteVecExt::grow_uninitialized (line 51) ... ok
[...]
?
On July 14, 2020 1:09 pm, Dominik Csapak wrote:
> this series adds the necessary bits and pieces for using a
> websocket connection in the api
>
> Dominik Csapak (9):
> proxmox/tools/byte_buffer: improve ByteBuffer interface
> proxmox/tools/byte_buffer: impl Default
> proxmox/tools/websocket: use ready macro for WebSocketWriter
> proxmox/tools/websocket: correctly return eof
> proxmox/tools/websocket: use io::Error and Result explicitely
> proxmox/tools/websocket: improve mask_bytes and create_frame interface
> proxmox/tools/websocket: implement send_control_frame for writer
> proxmox/tools/websocket: replace CallBack with a channel
> proxmox/tools/websocket: add WebSocket implementation
>
> proxmox/Cargo.toml | 3 +-
> proxmox/src/tools/byte_buffer.rs | 97 ++++++----
> proxmox/src/tools/websocket.rs | 296 +++++++++++++++++++++++++------
> 3 files changed, 306 insertions(+), 90 deletions(-)
>
> --
> 2.20.1
>
>
>
> _______________________________________________
> pbs-devel mailing list
> pbs-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
>
>
>
next prev parent reply other threads:[~2020-07-15 8:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 11:09 Dominik Csapak
2020-07-14 11:09 ` [pbs-devel] [PATCH proxmox 1/9] proxmox/tools/byte_buffer: improve ByteBuffer interface Dominik Csapak
2020-07-14 11:09 ` [pbs-devel] [PATCH proxmox 2/9] proxmox/tools/byte_buffer: impl Default Dominik Csapak
2020-07-14 11:09 ` [pbs-devel] [PATCH proxmox 3/9] proxmox/tools/websocket: use ready macro for WebSocketWriter Dominik Csapak
2020-07-14 11:09 ` [pbs-devel] [PATCH proxmox 4/9] proxmox/tools/websocket: correctly return eof Dominik Csapak
2020-07-14 11:09 ` [pbs-devel] [PATCH proxmox 5/9] proxmox/tools/websocket: use io::Error and Result explicitely Dominik Csapak
2020-07-14 11:09 ` [pbs-devel] [PATCH proxmox 6/9] proxmox/tools/websocket: improve mask_bytes and create_frame interface Dominik Csapak
2020-07-15 9:08 ` [pbs-devel] [PATCH proxmox v2 " Dominik Csapak
2020-07-14 11:09 ` [pbs-devel] [PATCH proxmox 7/9] proxmox/tools/websocket: implement send_control_frame for writer Dominik Csapak
2020-07-14 11:09 ` [pbs-devel] [PATCH proxmox 8/9] proxmox/tools/websocket: replace CallBack with a channel Dominik Csapak
2020-07-14 11:09 ` [pbs-devel] [PATCH proxmox 9/9] proxmox/tools/websocket: add WebSocket implementation Dominik Csapak
2020-07-15 8:15 ` Fabian Grünbichler [this message]
2020-07-15 8:31 ` [pbs-devel] [PATCH proxmox 0/9] preparation for websocket api Dominik Csapak
2020-07-15 13:00 ` [pbs-devel] applied: " Wolfgang Bumiller
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=1594800868.gpoilatxdp.astroid@nora.none \
--to=f.gruenbichler@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