Skip to content

Unarchive historian #687

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

Merged
merged 4 commits into from
Aug 7, 2025

Conversation

endothermicdev
Copy link
Contributor

This mostly just moves historian out of the archive directory, but I also fixed a minor bug for the greenlight use case. Finally, I'm trying to add support for the uv package manager while maintaining compatibility with poetry. If all goes well, the intent is to migrate fully to uv, but for now I'd like to allow testing without breaking existing installation methods (reckless is getting a uv installer but existing nodes won't have that yet.)

Copy link
Collaborator

@chrisguida chrisguida left a comment

Choose a reason for hiding this comment

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

Awesome, thanks so much for submitting this, @endothermicdev!

Psyched to see historian rise again 🚀

ACK b839311

@chrisguida chrisguida force-pushed the unarchive_historian branch from b839311 to 3459b9f Compare July 24, 2025 21:21
Avoids a potential crash when serving gossip on greenlight.
Adds uv support for faster and more flexible environment management.
This also keeps support for poetry installation for the time being.
Eventually we should migrate, but this will allow testing reckless
support for uv while maintaining compatibility with older installations.
@chrisguida chrisguida force-pushed the unarchive_historian branch from 3459b9f to 426535b Compare August 5, 2025 19:19
@chrisguida chrisguida merged commit 7429ade into lightningd:master Aug 7, 2025
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants