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

bug(driver-mxc): test helper fails to compile after gateway-name argument

未關閉 適合新手
#4,191 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

@feloy 已經在處理了。

開始於 2026年10月5日。

  • #4194 來自 @feloy —— 未關閉

評估

難度
1/5
預估耗時
1 小時以內
新手友好度
88/100
Issue 類型
缺陷
描述清晰度
描述清楚
活躍度
活躍
技術堆疊
rust
領域
testing

研究方向

閱讀 crates/openshell-driver-mxc/src/driver.rs 第 458 行附近的程式碼,並將 new_mocked 與其他 MXC 測試建構函式進行比較。執行適用於 x64 或 ARM64 的 Windows lint 工作,以重現編譯失敗;當 MXC 程式庫測試目標編譯成功,且 Windows 測試步驟可以執行時,即表示完成。

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

描述

state:triage-needed

User Story

I use an OpenShell source checkout on Windows to run the project's MSVC validation. Running windows:lint:x64 directly encountered a compile error in the MXC driver's test helper, so I cannot complete Windows lint or reach the test step.

Problem Statement

MxcComputeBackend::new now requires (gateway_name, config), but the test-only MxcComputeBackend::new_mocked helper still calls Self::new(config) in crates/openshell-driver-mxc/src/driver.rs:458. The Windows lint task includes all targets, so it compiles this #[cfg(test)] call and fails with E0277 and E0061.

Impact / Why This Matters

The current OpenShell source cannot complete Windows MSVC lint on x64; the same test target is part of the ARM64 lint task. Validation stops before Windows tests can run. Developers must patch the source locally to continue, which means the checked-in validation lane cannot confirm unrelated changes.

Acceptance Criteria

  • The MXC library test target compiles during Windows MSVC lint on x64 and ARM64 without E0277 or E0061.
  • The mocked backend uses a gateway name consistent with the driver's other test constructors.
  • The Windows MSVC test steps can run after lint passes.

Reproduction Steps

  1. Check out OpenShell main at 71c3cd957abef062eb7f37010056717cd49f2ed3 on a Windows machine with the repository's MSVC prerequisites.
  2. Run mise run --skip-tools windows:lint:x64. On a native ARM64 machine, use windows:lint:arm64.
  3. Observe the compile errors at crates/openshell-driver-mxc/src/driver.rs:458.

Environment

  • OpenShell: main at 71c3cd957abef062eb7f37010056717cd49f2ed3
  • OS: Windows, x64 MSVC validation
  • Rust: 1.95.0 from rust-toolchain.toml
  • Deployment: none required; this is a source checkout lint failure

Logs

error[E0277]: the trait bound `String: From<MxcComputeConfig>` is not satisfied
  --> crates/openshell-driver-mxc/src/driver.rs:458:37
error[E0061]: this function takes 2 arguments but 1 argument was supplied
  --> crates/openshell-driver-mxc/src/driver.rs:458:27
458 | let mut backend = Self::new(config);

Investigation

Commit a875add23 in PR #3264 added the gateway-name parameter to MxcComputeBackend::new for ETW event attribution but did not update new_mocked. The MXC implementation is gated to Windows, so non-Windows checks do not compile this call. Other MXC tests already use openshell_core::config::DEFAULT_GATEWAY_NAME when constructing the backend.

主要語言
Rust
星號
15.4k
分支
1.7k
平均合併
1 天 20 小時
30 天內合併 PR
348

環境準備

從這裡開始

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

NVIDIA/OpenShell 的其他 Issue

查看 NVIDIA/OpenShell 的全部 Issue

相似的 Issue

更多 Rust Issue

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

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