[Feature Request] Add Retry to `translate` when using the `QCtrl` integration

未关闭
#9 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
rust
领域
api

调研方向

首先跟踪 Rust 的 translate 调用,并将其行为与 submit 和现有的 ExecutionOptions 设置进行比较。检查 TranslationOptions 的定义方式,并确定预期的重试和超时行为;当长时间运行的 QCtrl 翻译不再因报告的临时超时而失败,并且相关设置已记录或经过测试时,工作即告完成。

由索引模型根据 Issue 内容生成。

描述

We've been testing the qcs client internally with the QCtrl flag enabled and noticed some timeouts when attempting to call translate on some large, iterative QAOA workloads. We've monitored our production logs here at Q-CTRL when running these tasks, and noticed that the compilation tasks are being handled correctly. They do take a while since this is a large circuit thats quite deep. Average compilation task time is ~50 seconds.

The client's translate call is timing out with the following error:

  File "/home/ssm-user/src/research-qccf-finance-optimization/qctrlQCCFresearchtools/platforms/rigetti_platform.py", line 159, in run
    executable = translate(
                 ^^^^^^^^^^
translation.TranslationError: Call failed during gRPC request: status: Unavailable, message: "unavailable", details: [], metadata: MetadataMap { headers: {"server": "awselb/2.0", "date": "Mon, 09 Jun 2025 18:27:52 GMT", "content-type": "application/grpc", "content-length": "0"} }

@erichulburd mentioned to us that a good possible solution here would be to have a retry around these translate calls. Possibly we could even have exposed timeout settings in the TranslationOptions? I know the submit function has similar settings available through the ExecutionOptions.

Attached is a full log from one of our QAOA runs with Rust debug logging enabled. Happy to help in anyway to get this implemented!

rigetti_output.log

主要语言
Rust
星标
3
派生
2
PR 合并指标
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

rigetti/qcs-api-client-rust 的其他 Issue

查看 rigetti/qcs-api-client-rust 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。