Skip to content

Conversation

@jasagredo
Copy link
Contributor

No description provided.

Copy link
Contributor

@bladyjoker bladyjoker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure how interleaved those events might be, but that might render the whole thing very difficult to work with.

Imagine a scenario where the newLSMLedgerTablesHandle is called concurrently N times, we have no way of matching Rising to Falling edges (bracket matching problem for logs basically).

If these calls or entirely sequential, then the current logging would be sufficient as there'd be no interleaving.

@jasagredo
Copy link
Contributor Author

This is mostly sequential, if not entirely, but this lets us disambiguate whether a deadlock happens in LSM or in Consensus code.

@jasagredo jasagredo enabled auto-merge December 26, 2025 11:08
@jasagredo jasagredo mentioned this pull request Dec 26, 2025
18 tasks
@jasagredo jasagredo added this pull request to the merge queue Dec 26, 2025
Merged via the queue into main with commit 7a549f1 Dec 26, 2025
17 of 19 checks passed
@jasagredo jasagredo deleted the js/more-tracing-lsm branch December 26, 2025 13:02
@github-project-automation github-project-automation bot moved this from 👀 In review to ✅ Done in Consensus Team Backlog Dec 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: ✅ Done

Development

Successfully merging this pull request may close these issues.

3 participants