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

[Code]: DAOSpace GlobalProposals not removed after being executed or rejected. #143

Closed
pause125 opened this issue Sep 22, 2022 · 4 comments · Fixed by #145
Closed

[Code]: DAOSpace GlobalProposals not removed after being executed or rejected. #143

pause125 opened this issue Sep 22, 2022 · 4 comments · Fixed by #145
Assignees
Labels
enhancement New feature or request

Comments

@pause125
Copy link
Collaborator

GlobalProposals is never removed after being executed or rejected.

The vector is always growing, there may have state explosion issue.

@pause125 pause125 added the enhancement New feature or request label Sep 22, 2022
@pause125 pause125 modified the milestone: v12 Sep 22, 2022
@jolestar
Copy link
Member

also, need to add max limit to GlobalProposals

if(exists<GlobalProposalActions>(dao_address)){
//TODO add limit to max global proposal action indexs before support Table
let current_global_proposal_actions = borrow_global_mut<GlobalProposalActions>(dao_address);
Vector::append(&mut current_global_proposal_actions.proposal_action_indexs, proposal_action_indexs);

@pause125
Copy link
Collaborator Author

pause125 commented Sep 22, 2022

Delete proposal after executed or rejected directly? Is there a need to keep them for querying history proposal info?

@jolestar
Copy link
Member

Delete proposal after executed or rejected directly. Is there a need to keep them for querying history proposal info?

I think they can bean deleted. The history proposal can query from history state or off-chain index DB.

@pause125
Copy link
Collaborator Author

ok, I will fix it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants