Skip to content
This repository was archived by the owner on Nov 15, 2023. It is now read-only.
This repository was archived by the owner on Nov 15, 2023. It is now read-only.

Alliance: member can't retire if was set once up for kicking #11936

@muharem

Description

@muharem

Description of bug

One of the requirements to retire and return deposit is to be not considered by alliance to be kicked - link.
To keep track of all members proposed for kicking there is a storage map with AccountIDs (UpForKicking) - link.

When Alliance proposes proposal with the call to kick_member, the pallet stores the account id in UpForKicking - link.
And when member is kicked, the AccountId is removed from UpForKicking storage - link.

But what If the proposal for kicking member is not voted to be executed and closed?
The AccountId will not be removed from the UpForKicking storage. And a member wont be able ever to retire.

Metadata

Metadata

Assignees

Labels

I3-bugThe node fails to follow expected behavior.Z1-easyCan be fixed primarily by duplicating and adapting code by an intermediate coder

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions