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 setExpenditurePayouts logic #1154

Merged
merged 1 commit into from
Aug 14, 2023
Merged

Conversation

area
Copy link
Member

@area area commented Aug 11, 2023

The setExpenditurePayouts logic is incorrect in the core contracts. When multiple values were set with the same call, the funding pot payouts property would not be updated / set correctly.

The updated/added test fail without the contracts changes, demonstrating the issue.

I don't believe we need to take any actions in terms of checking for 'wrong' expenditures - they're not used in the frontend (yet - development of expenditures surfaced this issue), and the consequences are 'only' that in the case of expenditures with multiple payouts, some payouts will need a new expenditure made. Funds are incorrectly returned to the domain containing the expenditure, so they can be used to pay out again via another expenditure.

Copy link
Member

@kronosapiens kronosapiens left a comment

Choose a reason for hiding this comment

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

@kronosapiens kronosapiens merged commit ea274ba into develop Aug 14, 2023
2 checks passed
@kronosapiens kronosapiens deleted the fix/setExpenditurePayouts branch August 14, 2023 12:24
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.

2 participants