Go to file
Dominik Csapak 62461aac4a proxmox/tools/websocket: introduce WebSocketError and use it
this patch introduces a custom WebSocketError, so that we can
detect errors in the websocket protocol and react to it in the
right way

the channel now sends a Result<(OpCode, Box<[u8]>), WebSocketError>
so that we can either react to a control frame, or react to an
errornous data stream (which means sending a close frame
with the appropriate error code)

while at it, change FrameHeader::try_from_bytes to return
Result<Option<FrameHeader>, WebSocketError> instead of a nested
Result with the *guessed* remaining size. This was neither used by
us, nor was it really meaningful, since this can change during the
decode every time new data is read (extensions, mask, payload length, etc.)
so simply returning an Option is enough information for us

Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
2020-07-17 14:34:52 +02:00
.cargo cargo: switch to use packaged crates by default 2020-01-03 09:39:52 +01:00
proxmox proxmox/tools/websocket: introduce WebSocketError and use it 2020-07-17 14:34:52 +02:00
proxmox-api-macro api-macro: formatting fixups 2020-07-16 14:13:14 +02:00
proxmox-sortable-macro bump proxmox-sortable-macro to 0.1.1 2020-04-17 18:37:46 +02:00
.gitignore add Cargo.lock to .gitignore 2020-01-15 17:10:13 +01:00
build.sh build.sh: point to system compiler via rust-toolchain 2020-01-15 16:25:14 +01:00
Cargo.toml merge api, sys and tools into proxmox directly 2020-01-21 12:15:42 +01:00
Makefile buildsys: drop format check in check target 2020-03-16 12:21:14 +01:00
README.rst README: Remove 'Versioning', add 'Steps for Releases' 2020-01-15 14:26:06 +01:00
rustfmt.toml initial import, starting with vec & io helpers 2019-06-06 14:00:25 +02:00

Local cargo config
==================

This repository ships with a ``.cargo/config`` that replaces the crates.io
registry with packaged crates located in ``/usr/share/cargo/registry``.

A similar config is also applied building with dh_cargo. Cargo.lock needs to be
deleted when switching between packaged crates and crates.io, since the
checksums are not compatible.

To reference new dependencies (or updated versions) that are not yet packaged,
the dependency needs to point directly to a path or git source.

Steps for Releases
==================

- Cargo.toml updates:
  - Bump all modified crate versions.
  - Update all the other crates' Cargo.toml to depend on the new versions if
    required, then bump their version as well if not already done.
- Update debian/changelog files in all the crates updated above.
- Build packages with `make deb`.