Add guide on replaying a ledger with stellar-core - #2885
Merged
Merged
Conversation
Contributor
Contributor
tamirms
approved these changes
Sep 30, 2026
leighmcculloch
marked this pull request as ready for review
September 30, 2026 12:02
Copilot stopped reviewing on behalf of
leighmcculloch due to an error
September 30, 2026 12:02
Contributor
|
PR Preview: torn down |
Contributor
There was a problem hiding this comment.
Note
Copilot was unable to run its full agentic suite in this review.
Copilot review overview
Review effort: Lite
Findings: 1
Open (2)
What changed in this PR
Adds a new developer guide page describing how to replay a Stellar ledger using Stellar Core to re-generate LedgerCloseMeta (including diagnostic events), and makes it reachable via the site routes.
Changes:
- Added a new docs page: “Replay a ledger to collect its LedgerCloseMeta”
- Registered the new guide route in
routes.txt
| File | Description |
|---|---|
| routes.txt | Adds the docs route for the new replay guide so it’s discoverable/routable. |
| docs/build/guides/events/replay-ledger-close-meta.mdx | New guide content explaining end-to-end replay, extraction, and diagnostic event analysis workflow. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
|
|
||
| ``` | ||
| Collect the LedgerCloseMeta for transaction ____ from ledger ____ and analyse from the diagnostic events why it failed. Follow the steps in: | ||
| https://developers.stellar.org/docs/build/guides/events/replay-ledger-close-meta.md |
| An AI coding agent can do all of this for you. Give it a prompt that links to this guide, like: | ||
|
|
||
| ``` | ||
| Collect the LedgerCloseMeta for transaction ____ from ledger ____ and analyse from the diagnostic events why it failed. Follow the steps in: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Add a how-to guide on replaying a single ledger with stellar-core to collect its LedgerCloseMeta with diagnostic events, using a failed Mainnet contract call as the worked example.
Why
It's possible to do this, but discovering how is not intuitive.
Read It
https://developers-pr-2885.previews.kube001.services.stellar-ops.com/docs/build/guides/events/replay-ledger-close-meta