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

fix: Fix Wallet Reward Computing Job - MEED-2455 - Meeds-io/meeds#1086 #408

Merged
merged 1 commit into from
Sep 5, 2023

Conversation

boubaker
Copy link
Member

@boubaker boubaker commented Sep 5, 2023

Prior to this fix, the Wallet Rewarding Job is sometimes executed at the same time then the rewards sending. This change ensure to not asynchronously compute rewards at the same time than executing a Reward Period Sending storage operation.

Prior to this fix, the Wallet Rewarding Job is sometimes executed at the same time then the rewards sending. This change ensure to not asynchronously sompute rewards at the same time than executing a Reward Period Sending storage operation.
@sonarcloud
Copy link

sonarcloud bot commented Sep 5, 2023

SonarCloud Quality Gate failed.    Quality Gate failed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

41.2% 41.2% Coverage
0.0% 0.0% Duplication

idea Catch issues before they fail your Quality Gate with our IDE extension sonarlint SonarLint

@boubaker boubaker merged commit d2834c3 into develop Sep 5, 2023
2 of 3 checks passed
@boubaker boubaker deleted the meed-2455-develop branch September 5, 2023 18:12
exo-swf pushed a commit that referenced this pull request Sep 6, 2023
#408)

Prior to this fix, the Wallet Rewarding Job is sometimes executed at the
same time then the rewards sending. This change ensure to not
asynchronously compute rewards at the same time than executing a Reward
Period Sending storage operation.
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