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

Added new config for rewards #6841

Merged
merged 6 commits into from
Mar 5, 2025
Merged

Conversation

sstanculeanu
Copy link
Collaborator

Reasoning behind the pull request

  • new config for rewards + fix usage based on epoch

Proposed changes

  • added new config for rewards
  • proper handle based on epochs for rewards config
  • removed duplicated economics mock

Testing procedure

  • standard system test + check new sustainability address

Pre-requisites

Based on the Contributing Guidelines the PR author and the reviewers must check the following requirements are met:

  • was the PR targeted to the correct branch?
  • if this is a larger feature that probably needs more than one PR, is there a feat branch created?
  • if this is a feat branch merging, do all satellite projects have a proper tag inside go.mod?

@sstanculeanu sstanculeanu changed the base branch from master to rc/rewards-config February 27, 2025 13:46
Copy link

⚠️ No report was generated due to an error or cancellation of the process.
Please checkout gh action logs for details

@sstanculeanu
Copy link
Collaborator Author

Run Tests:
mx-chain-simulator-go: main
mx-chain-testing-suite: main

Copy link

📊 MultiversX Automated Test Report: View Report

🔄 Build Details:

  • mx-chain-go Commit Hash: d44a2639c065665dda3283fa7eb535a904265ee8
  • Current Branch: new_rewards_config
  • mx-chain-go Target Branch: master
  • mx-chain-simulator-go Target Branch: main
  • mx-chain-testing-suite Target Branch: main

🚀 Environment Variables:

  • TIMESTAMP: 27022025-135828
  • PYTEST_EXIT_CODE: 0
    🎉 MultiversX CI/CD Workflow Complete!

Copy link

📊 MultiversX Automated Test Report: View Report

🔄 Build Details:

  • mx-chain-go Commit Hash: 55c3a39fccbcbaf0b83d6f7939a776f5f8ca60ff
  • Current Branch: new_rewards_config
  • mx-chain-go Target Branch: master
  • mx-chain-simulator-go Target Branch: main
  • mx-chain-testing-suite Target Branch: main

🚀 Environment Variables:

  • TIMESTAMP: 27022025-141851
  • PYTEST_EXIT_CODE: 0
    🎉 MultiversX CI/CD Workflow Complete!

Copy link

📊 MultiversX Automated Test Report: View Report

🔄 Build Details:

  • mx-chain-go Commit Hash: 94626ba6bb0d04696576a00d72e930af159a3534
  • Current Branch: new_rewards_config
  • mx-chain-go Target Branch: master
  • mx-chain-simulator-go Target Branch: main
  • mx-chain-testing-suite Target Branch: main

🚀 Environment Variables:

  • TIMESTAMP: 27022025-142010
  • PYTEST_EXIT_CODE: 0
    🎉 MultiversX CI/CD Workflow Complete!

Copy link

📊 MultiversX Automated Test Report: View Report

🔄 Build Details:

  • mx-chain-go Commit Hash: 37ab7adf9127ebb335c53ad8894b9c23004684e0
  • Current Branch: master
  • mx-chain-go Target Branch: ``
  • mx-chain-simulator-go Target Branch: main
  • mx-chain-testing-suite Target Branch: main

🚀 Environment Variables:

  • TIMESTAMP: 27022025-143232
  • PYTEST_EXIT_CODE: 0
    🎉 MultiversX CI/CD Workflow Complete!

Copy link

📊 MultiversX Automated Test Report: View Report

🔄 Build Details:

  • mx-chain-go Commit Hash: de8c129e0647c82e8738c09c304d61483b640414
  • Current Branch: new_rewards_config
  • mx-chain-go Target Branch: rc/rewards-config
  • mx-chain-simulator-go Target Branch: main
  • mx-chain-testing-suite Target Branch: main

🚀 Environment Variables:

  • TIMESTAMP: 27022025-143258
  • PYTEST_EXIT_CODE: 0
    🎉 MultiversX CI/CD Workflow Complete!

return nil, 0, epochStart.ErrNilProtocolSustainabilityAddress
}

address, err := brc.pubkeyConverter.Decode(protocolSustainabilityAddressForEpoch)
Copy link
Contributor

Choose a reason for hiding this comment

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

you should make the decodes only once - when creating the setup. Not at every epoch.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

indeed we should detect any config error as early as possible, pushed

@sstanculeanu
Copy link
Collaborator Author

Run Tests:
mx-chain-simulator-go: main
mx-chain-testing-suite: main

sasurobert
sasurobert previously approved these changes Feb 28, 2025
Copy link

📊 MultiversX Automated Test Report: View Report

🔄 Build Details:

  • mx-chain-go Commit Hash: 37ab7adf9127ebb335c53ad8894b9c23004684e0
  • Current Branch: master
  • mx-chain-go Target Branch: ``
  • mx-chain-simulator-go Target Branch: main
  • mx-chain-testing-suite Target Branch: main

🚀 Environment Variables:

  • TIMESTAMP: 28022025-120849
  • PYTEST_EXIT_CODE: 0
    🎉 MultiversX CI/CD Workflow Complete!

Copy link

📊 MultiversX Automated Test Report: View Report

🔄 Build Details:

  • mx-chain-go Commit Hash: c8906c82b30f349bf68f473ef0737cfbfc6df9a8
  • Current Branch: new_rewards_config
  • mx-chain-go Target Branch: rc/rewards-config
  • mx-chain-simulator-go Target Branch: main
  • mx-chain-testing-suite Target Branch: main

🚀 Environment Variables:

  • TIMESTAMP: 28022025-120917
  • PYTEST_EXIT_CODE: 0
    🎉 MultiversX CI/CD Workflow Complete!

danidrasovean
danidrasovean previously approved these changes Mar 4, 2025
Copy link
Collaborator

@danidrasovean danidrasovean left a comment

Choose a reason for hiding this comment

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

Normal allin test: master-37ab7adf91 -> new_rewards_config-c8906c82b3

--- Specific errors ---

block hash does not match 11
wrong nonce in block 31
miniblocks does not match 0
num miniblocks does not match 0
miniblock hash does not match 0
block bodies does not match 0
receipts hash missmatch 0

/------/

--- Statistics ---

Nr. of all ERRORS: 0
Nr. of all WARNS: 239
Nr. of new ERRORS: 0
Nr. of new WARNS: 0
Nr. of PANICS: 0
Nodes with panic: []

/------/

--- System test go ---

All scenarios from system-test-go are OK!
/------/

rewardsHandler := &economicsmocks.EconomicsHandlerStub{
RewardsTopUpGradientPointCalled: func() *big.Int {
rewardsHandler := &economicsmocks.EconomicsHandlerMock{
RewardsTopUpGradientPointInEpochCalled: func(epoch uint32) *big.Int {
Copy link
Contributor

Choose a reason for hiding this comment

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

unused epoch argument, maybe use an _ ?

return big.NewInt(0).Set(rewardsTopUpGradientPoint)
},
RewardsTopUpFactorCalled: func() float64 {
RewardsTopUpFactorInEpochCalled: func(epoch uint32) float64 {
Copy link
Contributor

Choose a reason for hiding this comment

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

unused epoch argument

Copy link

github-actions bot commented Mar 5, 2025

⚠️ No report was generated due to an error or cancellation of the process.
Please checkout gh action logs for details

@sstanculeanu
Copy link
Collaborator Author

Run Tests:
mx-chain-simulator-go: main
mx-chain-testing-suite: main

Copy link

github-actions bot commented Mar 5, 2025

📊 MultiversX Automated Test Report: View Report

🔄 Build Details:

  • mx-chain-go Commit Hash: 37ab7adf9127ebb335c53ad8894b9c23004684e0
  • Current Branch: master
  • mx-chain-go Target Branch: ``
  • mx-chain-simulator-go Target Branch: main
  • mx-chain-testing-suite Target Branch: main

🚀 Environment Variables:

  • TIMESTAMP: 05032025-155526
  • PYTEST_EXIT_CODE: 0
    🎉 MultiversX CI/CD Workflow Complete!

Copy link

github-actions bot commented Mar 5, 2025

📊 MultiversX Automated Test Report: View Report

🔄 Build Details:

  • mx-chain-go Commit Hash: 35d5b4ee64bc51be4971229efca94fe707937e7e
  • Current Branch: new_rewards_config
  • mx-chain-go Target Branch: rc/rewards-config
  • mx-chain-simulator-go Target Branch: main
  • mx-chain-testing-suite Target Branch: main

🚀 Environment Variables:

  • TIMESTAMP: 05032025-155826
  • PYTEST_EXIT_CODE: 0
    🎉 MultiversX CI/CD Workflow Complete!

@sstanculeanu sstanculeanu merged commit de61749 into rc/rewards-config Mar 5, 2025
8 checks passed
@sstanculeanu sstanculeanu deleted the new_rewards_config branch March 5, 2025 16:09
@sstanculeanu sstanculeanu restored the new_rewards_config branch March 5, 2025 16:10
@sstanculeanu sstanculeanu deleted the new_rewards_config branch March 5, 2025 17:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants