Skip to content

Conversation

@adonagy
Copy link
Contributor

@adonagy adonagy commented Dec 2, 2024

closes #383

@adonagy adonagy changed the title Feat/archive compatibility Archive node compatibility Dec 2, 2024
@adonagy adonagy force-pushed the feat/archive-compatibility branch from cbb24b3 to 81f9bda Compare December 11, 2024 13:09
@adonagy adonagy force-pushed the feat/archive-compatibility branch 4 times, most recently from 107a928 to c07fa11 Compare January 13, 2025 10:01
@adonagy adonagy marked this pull request as ready for review January 13, 2025 10:01
@adonagy adonagy requested review from sebastiencs and tizoc January 13, 2025 10:01
@tizoc
Copy link
Collaborator

tizoc commented Jan 13, 2025

General comment because it happens at many places in the diff: is passing the is_archive boolean around everywhere the best option? Since most of the time the value is false I would rather leave the current constructors as-is, and then either have an extra method that takes care of setting up the archive node requirements when called (not sure how viable it is, just an idea)

@adonagy adonagy force-pushed the feat/archive-compatibility branch from e986937 to c56c227 Compare January 27, 2025 10:22
@adonagy adonagy merged commit 88835eb into develop Jan 27, 2025
11 checks passed
@adonagy adonagy deleted the feat/archive-compatibility branch January 27, 2025 12:58
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.

As a developer, I want to integrate archive node capability into the rust node, so we can use it with the producer dashboard

5 participants