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

Correctly initialize the txpool as disabled on creation #6890

Conversation

fab-10
Copy link
Contributor

@fab-10 fab-10 commented Apr 5, 2024

PR description

Correctly initialize the txpool as disabled on creation, to avoid exception when calling txpool methods before the initial sync phase is done.

Fixed Issue(s)

fixes #6863

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:

  • unit tests: ./gradlew build
  • acceptance tests: ./gradlew acceptanceTest
  • integration tests: ./gradlew integrationTest
  • reference tests: ./gradlew ethereum:referenceTests:referenceTests

@fab-10 fab-10 force-pushed the fix-calling-disabled-txpool-when-initial-sync branch from a5285e7 to ff02848 Compare April 5, 2024 10:24
@fab-10 fab-10 marked this pull request as ready for review April 5, 2024 12:06
Copy link
Contributor

@gfukushima gfukushima left a comment

Choose a reason for hiding this comment

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

lgtm


@Test
public void txPoolStartsEnabledWhenFullSyncConfigured() {
// when using FULL sync, txpool starts enabled, because it could be
Copy link
Contributor

Choose a reason for hiding this comment

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

Glad that you added this comment here, I was wondering why we enable txpool on full sync thinking of a node that is still syncing up to head when I first read the test name.

@macfarla macfarla enabled auto-merge (squash) April 8, 2024 06:56
@macfarla macfarla merged commit f26f3f5 into hyperledger:main Apr 8, 2024
42 checks passed
amsmota pushed a commit to Citi/besu that referenced this pull request Apr 16, 2024
…6890)

Signed-off-by: Fabio Di Fabio <[email protected]>
Co-authored-by: Sally MacFarlane <[email protected]>
Signed-off-by: amsmota <[email protected]>
amsmota pushed a commit to Citi/besu that referenced this pull request Apr 16, 2024
…6890)

Signed-off-by: Fabio Di Fabio <[email protected]>
Co-authored-by: Sally MacFarlane <[email protected]>
Signed-off-by: amsmota <[email protected]>
macfarla added a commit to macfarla/besu that referenced this pull request Apr 26, 2024
matthew1001 pushed a commit to kaleido-io/besu that referenced this pull request Jun 7, 2024
@fab-10 fab-10 deleted the fix-calling-disabled-txpool-when-initial-sync branch November 8, 2024 16:37
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.

NPE when making a JSON/RPC call too early that requires the transaction pool to be initialized
3 participants