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

cmd, common, eth: copy constants after get chain id #866

Merged
merged 1 commit into from
Feb 18, 2025

Conversation

gzliudan
Copy link
Collaborator

@gzliudan gzliudan commented Feb 18, 2025

Proposed changes

The PR #850 sets network ID automatically. And the PR #846 copy constants during XDC startup. But when the flag NetworkIdFlag is not provide by script, the function common.CopyConstans in SetEthConfig does not work. So I move it into the function New in the file eth/backend.go after networkID has been determined.

Types of changes

What types of changes does your code introduce to XDC network?
Put an in the boxes that apply

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation Update (if none of the other choices apply)
  • Regular KTLO or any of the maintaince work. e.g code style
  • CICD Improvement

Impacted Components

Which part of the codebase this PR will touch base on,

Put an in the boxes that apply

  • Consensus
  • Account
  • Network
  • Geth
  • Smart Contract
  • External components
  • Not sure (Please specify below)

Checklist

Put an in the boxes once you have confirmed below actions (or provide reasons on not doing so) that

  • This PR has sufficient test coverage (unit/integration test) OR I have provided reason in the PR description for not having test coverage
  • Provide an end-to-end test plan in the PR description on how to manually test it on the devnet/testnet.
  • Tested the backwards compatibility.
  • Tested with XDC nodes running this version co-exist with those running the previous version.
  • Relevant documentation has been updated as part of this PR
  • N/A

@gzliudan gzliudan force-pushed the fix_constants branch 2 times, most recently from d55fe92 to e431f12 Compare February 18, 2025 07:15
@gzliudan gzliudan merged commit dead639 into XinFinOrg:dev-upgrade Feb 18, 2025
13 checks passed
@gzliudan gzliudan deleted the fix_constants branch February 18, 2025 07:51
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