-
Notifications
You must be signed in to change notification settings - Fork 3
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
Can no longer mark a failed meetup as completed #275
Comments
@clangenb Before fixing this, I would like to understand the purpose of There is no "completed meetup". Line 560 in 615c292
The key is inserted when the rewards have been successfully issued: Line 1893 in 615c292
and in the registration phase, when we cannot get the participants who are eligible for the reward: Line 597 in 615c292
What if claim_reward fails for other reasons? If the problem is only at Line 597 in 615c292
IssuedRewards<T> ?
|
…` storage. (#274) * claim_rewards_error_results_in_meetup_marked_as_completed fails * remove debug print messages * Fix bug #275: - Add a claim_reward feedback in the IssuedRewards Storage - claim_reward returns OK if a MeetupValidationError occurs in the Registration phase * rename claim_reward_successfull * Add Cargo.lock which was falsely deleted * Fix to compile in std and no_std mode * Use of strongly typed MeetupResult * Rename test * Add missing /std into std features * Changes from review * Changes from review: OptionQuery Co-authored-by: echevrier <edith.chevrier@scs.ch>
Since paritytech/substrate#11927 changes, the storage don't persist when a call return an error. See paritytech/substrate#11533 (comment)
So
pallets/ceremonies/src/lib.rs
Line 597 in 615c292
The test claim_rewards_error_results_in_meetup_marked_as_completed fails at
pallets/ceremonies/src/tests.rs
Line 1040 in 615c292
The text was updated successfully, but these errors were encountered: