native/pinocchio examples: deploy script points at program.so, which the build never produces

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

  • #702 来自 @MarkFeder —— 已关闭,未合并

评估

难度
1/5
预计耗时
1 小时以内
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
停滞
技术栈
rust
领域
blockchain, devops

调研方向

Locate the deploy npm scripts and cicd.sh files in the single-program native and Pinocchio examples. Read each cargo build-sbf command to confirm the crate-named .so artifact, then check that deploy uses the proposed wildcard and that multi-program and asm examples remain untouched. Done when the single-program deploy steps resolve the built artifact.

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

描述

accepted

The deploy npm script and cicd.sh in the single-program native and Pinocchio examples run:

solana program deploy ./program/target/so/program.so

cargo build-sbf --sbf-out-dir=./program/target/so names the artifact after the crate (e.g. transfer_tokens_program.so), so program.so never exists and the documented deploy step fails with "No such file". CI doesn't run deploy, which is why it went unnoticed.

Proposed fix: deploy ./program/target/so/*.so, which resolves to the single artifact in each of these examples. Multi-program examples and the asm example are left alone. Implementation is ready in #702.

主要语言
Rust
星标
1.4k
派生
559
平均合并
20 小时 9 分钟
30 天内合并 PR
17

环境准备

从这里开始

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

solana-foundation/program-examples 的其他 Issue

查看 solana-foundation/program-examples 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

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