Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

[Proposal][desktop-gpui] Startup Upload Health Check & Pre-Recording Bandwidth Diagnostics (follow-up to #73 / #3188)

Offen
  • Stimmt etwas nicht?
#3,218 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
35/100
Issue-Typ
Feature
Klarheit
Muss geklärt werden
Aktivitätsstatus
Aktiv
Tech-Stack
rust
Bereich
desktop

Rechercherichtung

This is a design proposal awaiting a maintainer decision (Option A vs B) on apps/desktop-gpui before any code should be written. Start by reading apps/desktop-gpui/src/upload.rs, diagnostics.rs, recording.rs and main_window.rs to understand the existing upload client and header handling, and review the linked prior discussion in #3188 and #73. Done means an aligned product decision plus implementation of the startup health check, warning badge, and pre-recording speed probe with cancellation via saturating_sub/checked_sub.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Following up on @richiemcilroy's feedback on #3188 (and #73) regarding the transition from legacy apps/desktop (Tauri) to the native GPUI app (apps/desktop-gpui), opening this issue first so we can align on the product behavior before writing any code.

Proposed Scope for apps/desktop-gpui

  1. Startup Upload Connectivity & Storage Health Check (apps/desktop-gpui/src/upload.rs & diagnostics.rs)

    • Run a lightweight, non-blocking startup check using the existing authenticated client (preserving apply_env_headers / preview bypass headers) and verifying actual S3/storage write readiness rather than a no-op body discard.
    • Surface a subtle warning badge in main_window.rs if upload connectivity or storage reachability is degraded, with a one-click diagnostics detail view.

  2. Pre-Recording Upload Speed Probe & Resolution Behavior (apps/desktop-gpui/src/recording.rs)

    • Execute a one-shot probe prior to recording start (cancelled immediately before clean_capture::prepare on all platforms including Linux, using Duration::saturating_sub / checked_sub).
    • Product Question for @richiemcilroy: For apps/desktop-gpui, would you prefer:
      • (Option A - Advisory Warning / Opt-in): Keep the user's selected capture resolution intact by default and show a non-intrusive recommendation banner when upload throughput is below threshold, or
      • (Option B - Automatic Instant-Mode Cap): Automatically cap resolution only for Instant Mode recordings (where real-time chunk upload matters) while leaving Studio Mode at full Resolution::Captured?

Happy to adjust the design to match your roadmap for apps/desktop-gpui before submitting a PR.

Vorherrschende Sprache
Rust
Sterne
23.7k
Forks
2.1k
Ø Merge
1 T. 11 Std.
Gemergte PRs (30 T.)
588

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus CapSoftware/Cap

Alle Issues in CapSoftware/Cap

Ähnliche Issues

Weitere Issues zu Rust

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.