Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(release): publish v1.2.1 #482

Merged
merged 1 commit into from
Jan 30, 2024
Merged

chore(release): publish v1.2.1 #482

merged 1 commit into from
Jan 30, 2024

Conversation

MicaiahReid
Copy link
Contributor

No description provided.

@MicaiahReid MicaiahReid requested a review from lgalabru January 30, 2024 16:34
Previously, when parsing and archive tsv to determine the canonical
fork, we would always start at block 0, even if there was a rocksdb
instance containing stacks chaindata. The entire fork was loaded in
memory and inserted.

Now, we start at the latest confirmed chaintip for this process, which
greatly reduces the memory footprint on subsequent startups of the
Chainhook service. Note: an initial run of the Chainhook service can
still use significant memory.
Copy link
Contributor

@lgalabru lgalabru left a comment

Choose a reason for hiding this comment

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

LGTM!

@MicaiahReid MicaiahReid merged commit 2eca8e3 into main Jan 30, 2024
11 checks passed
Copy link

🎉 This PR is included in version 1.2.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

2 participants