Skip to content

Comments

refactor: move isRevertReasonEnabled into DataStorageConfiguration#9858

Draft
kkaur01 wants to merge 3 commits intohyperledger:mainfrom
kkaur01:refactor-revert-reason-to-data-storage-config
Draft

refactor: move isRevertReasonEnabled into DataStorageConfiguration#9858
kkaur01 wants to merge 3 commits intohyperledger:mainfrom
kkaur01:refactor-revert-reason-to-data-storage-config

Conversation

@kkaur01
Copy link
Contributor

@kkaur01 kkaur01 commented Feb 20, 2026

PR description

Replace the two standalone boolean parameters (isRevertReasonEnabled,
isParallelTxProcessingEnabled) threaded through 8+ layers of the call stack with a single DataStorageConfiguration object, which is already the home of related storage concerns (receiptCompactionEnabled, etc.).

The --revert-reason-enabled CLI flag moves from BesuCommand into DataStorageOptions. No behaviour change.

Fixed Issue(s)

fixes #7597

Thanks for sending a pull request! Have you done the following?

  • Checked out our contribution guidelines?
  • Considered documentation and added the doc-change-required label to this PR if updates are required.
  • Considered the changelog and included an update if required.
  • For database changes (e.g. KeyValueSegmentIdentifier) considered compatibility and performed forwards and backwards compatibility tests

Locally, you can run these tests to catch failures early:

  • spotless: ./gradlew spotlessApply
  • unit tests: ./gradlew build
  • acceptance tests: ./gradlew acceptanceTest
  • integration tests: ./gradlew integrationTest
  • reference tests: ./gradlew ethereum:referenceTests:referenceTests
  • hive tests: Engine or other RPCs modified?

@kkaur01 kkaur01 marked this pull request as draft February 20, 2026 20:16
Closes hyperledger#7597

- Add `revertReasonEnabled` field to `DataStorageConfiguration`
  (alongside existing storage concerns like `receiptCompactionEnabled`)
- Move `--revert-reason-enabled` CLI option from `BesuCommand` into
  `DataStorageOptions` so it is serialised/deserialised with the rest
  of the data-storage group automatically
- Replace the two standalone boolean params `enableRevertReason` and
  `isParallelTxProcessingEnabled` in `MainnetProtocolSpecs`,
  `MainnetProtocolSpecFactory`, `ProtocolScheduleBuilder`,
  `MainnetProtocolSchedule` and all consensus schedule builders with a
  single `DataStorageConfiguration` object
- Remove now-redundant `isRevertReasonEnabled` / `isParallelTxProcessingEnabled`
  fields and setters from `BesuControllerBuilder`; all controller
  builders pass `dataStorageConfiguration` directly
- Fix `ProcessBesuNodeRunner` duplicate-flag bug: `--revert-reason-enabled`
  was being added both by `DataStorageOptions.getCLIOptions()` and
  explicitly; removed the explicit addition

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Signed-off-by: kkaur01 <kanchan.kaur@consensys.net>
@kkaur01 kkaur01 force-pushed the refactor-revert-reason-to-data-storage-config branch from 045b4a2 to f0509bc Compare February 21, 2026 01:22
kkaur01 and others added 2 commits February 21, 2026 12:43
…ation

Replace old boolean isRevertReasonEnabled param with DataStorageConfiguration
in all MainnetProtocolSchedule.fromConfig() calls.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Signed-off-by: kkaur01 <kanchan.kaur@consensys.net>
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.

BesuCommand.isRevertReasonEnabled belongs in DataStorageConfiguration

1 participant