Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Feature request: simple option to fast-forward ledgers in --local mode

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

首先跟踪 --local 的启动路径,以及现有的 ENABLE_CORE_MANUAL_CLOSE 和 /manualclose 流程。检查 Horizon、RPC 和 friendbot 如何在容器中启动,然后定义一种接受 N 个 ledger 且能与本地 stack 配合工作的推进机制。完成的标准是本地用户无需手动的两阶段流程即可快速推进 ledger。

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

描述

Quickstart is great for local development. It would be great to add a feature for advancing ledgers quickly.

What I'm trying to do

When testing against --local, the network starts at ledger 1, which doesn't look or behave much like testnet/mainnet (where ledger numbers are in the millions and time has visibly passed). I'd like a way to quickly fast-forward to a higher ledger number. Both for realistic UI testing and for exercising time-based contract logic without waiting a long time.

What I tried

I went down the ENABLE_CORE_MANUAL_CLOSE=true + curl /manualclose path. It works in principle but isn't really convenient:

  • Throughput is heavily bottlenecked when horizon/rpc are also enabled (their captive cores fall behind and constantly catch up). To get reasonable speed I had to disable everything except core, burn ledgers, then restart with horizon/rpc. But that two-phase workflow hits other rough edges: friendbot autostarts and crashes when horizon is disabled, taking down the container.
  • It's not obvious from the docs which env vars actually exist vs. don't. I tried things like STELLAR_CORE_FLAGS, ENABLE_FRIENDBOT, etc. that turned out to be silently ignored. The set of supported env vars and flags also seems to change between image versions, so older tutorials, or responses on Discord point at things that no longer work.

What would be ideal

An endpoint to automatically advance by N ledgers

主要语言
Shell
星标
225
派生
236
平均合并
1 天 12 小时
30 天内合并 PR
18

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

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

stellar/quickstart 的其他 Issue

查看 stellar/quickstart 的全部 Issue

相似的 Issue

更多 Shell/Bash Issue

把新 issue 发到你的邮箱

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