Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

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

未關閉
#3,218 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
35/100
Issue 類型
功能
描述清晰度
需要釐清
活躍度
活躍
技術堆疊
rust
領域
desktop

研究方向

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.

由索引模型根據 Issue 內容生成。

描述

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.

主要語言
Rust
星號
23.7k
分支
2.1k
平均合併
1 天 7 小時
30 天內合併 PR
697

環境準備

  • 提供 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

CapSoftware/Cap 的其他 Issue

查看 CapSoftware/Cap 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。