Skip to content

docs: document correct order of locking for LedgerContext#1626

Open
ozgb wants to merge 1 commit into
mainfrom
ozgb-document-lock-order
Open

docs: document correct order of locking for LedgerContext#1626
ozgb wants to merge 1 commit into
mainfrom
ozgb-document-lock-order

Conversation

@ozgb

@ozgb ozgb commented Jun 2, 2026

Copy link
Copy Markdown
Contributor

Overview

Follow-up from @Klapeyron's comment here: #1605 (comment)

Documents the correct order of aquisition for the mutexes in LedgerContext.

As part of this work, I verified that all current usage of the mutexes is correct.

🗹 TODO before merging

  • Ready

📌 Submission Checklist

  • All commits are signed off (git commit -s) for the DCO
  • Changes are backward-compatible (or flagged if breaking)
  • Pull request description explains why the change is needed
  • Self-reviewed the diff
  • I have included a change file, or skipped for this reason:
  • If the changes introduce a new feature, I have bumped the node minor version
  • Update documentation (if relevant)
  • Updated AGENTS.md if build commands, architecture, or workflows changed
  • No new todos introduced

🧪 Testing Evidence

Please describe any additional testing aside from CI:

  • Additional tests are provided (if possible)

🔱 Fork Strategy

  • Node Runtime Update
  • Node Client Update
  • Other:
  • N/A

Links

Signed-off-by: Oscar Bailey <79094698+ozgb@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants