Skip to content

[Research] [Do not merge] Claude generated comparison between protobuf, cap'n proto and flatbuffers#708

Draft
darioalessandro wants to merge 1 commit into
mainfrom
swap-transport
Draft

[Research] [Do not merge] Claude generated comparison between protobuf, cap'n proto and flatbuffers#708
darioalessandro wants to merge 1 commit into
mainfrom
swap-transport

Conversation

@darioalessandro

Copy link
Copy Markdown
Member

Type of Change

  • Bug fix
  • New feature
  • Enhancement
  • Breaking change
  • Project / Infra

Testing

  • Tests written or updated
  • No tests needed

Other

  • Documentation updated
  • Before/After Images provided

@github-actions

github-actions Bot commented Mar 4, 2026

Copy link
Copy Markdown

👋 Thanks for your contribution!

A maintainer will review your changes shortly.

✅ Automated Checks

CI/CD tests will run automatically. Please ensure all checks pass before requesting review.

🚀 Preview Deployments

Maintainers can test this PR in a live environment using these commands:

  • /build-images — Build Docker images for this PR (~10-15 min)
  • /deploy — Deploy preview environment (~3-5 min)
  • /build-and-deploy — Build images and deploy in one step (~15-20 min)
  • /undeploy — Tear down preview environment

Preview URLs will be posted automatically once deployed.

📚 PR Deployment Documentation

@darioalessandro darioalessandro changed the title [Research] [Do not merge] Claude generated comparison between protobug, cap'n proto and flatbuffers [Research] [Do not merge] Claude generated comparison between protobuf, cap'n proto and flatbuffers Mar 6, 2026
@testradav testradav marked this pull request as draft March 6, 2026 20:13
testradav pushed a commit to testradav/videocall-rs that referenced this pull request May 18, 2026
…E breakage

Resolves security-union#714. Under the priority-drop policy introduced in security-union#708,
AES_KEY was classified as `Control`, so it was never preemptively
dropped but COULD still be dropped silently at the channel level if
the relay's outbound channel hit true overflow (100% full). AES_KEY is
the symmetric half of the E2EE handshake (paired with RSA_PUB_KEY,
which is already Critical) — losing it breaks encrypted communication
for the affected peer pair with no `overflow_critical` label and no
page-able alert. Both halves of the handshake must be treated
symmetrically.

Changes:
- `OutboundPriority::classify` now classifies `PacketType::AES_KEY` as
  `Critical` (alongside `SESSION_ASSIGNED`, `CONGESTION`,
  `RSA_PUB_KEY`, `MEETING`).
- Module docstring and enum doc-comments updated to list AES_KEY in
  the Critical set, with a brief explanation of the E2EE-handshake
  rationale.
- Existing `classify_aes_key_is_control` test flipped to
  `classify_aes_key_is_critical`.
- `spec_critical_set_is_session_congestion_rsa_meeting` renamed to
  `spec_critical_set_is_session_congestion_rsa_aes_meeting` and
  extended to assert AES_KEY membership.
- `realchannel_critical_admit_even_at_99_percent_fill` extended to
  cover AES_KEY.
- New `aes_key_is_critical_and_never_dropped` test sweeps fill levels
  (0/50/80/90/95/99%) to lock in the never-preempt invariant.

Quality gates:
- `cargo fmt -p videocall-api` clean.
- `cargo clippy -p videocall-api --all-targets -- -D warnings` clean.
- `cargo test -p videocall-api --lib actors::priority_drop` — 37/37
  passing (36 previous tests + 1 new).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
testradav pushed a commit to testradav/videocall-rs that referenced this pull request May 18, 2026
…iority-drop-by-media-type

feat(relay): priority-aware drop policy on per-session outbound channel
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants