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

Support for account deletion in ledgers #15730

Draft
wants to merge 110 commits into
base: compatible
Choose a base branch
from
Draft

Conversation

rbonichon
Copy link
Member

@rbonichon rbonichon commented Jun 10, 2024

This is draft PR, intended to show and track implementation progress.

The commits at the moment are mostly informative and will be rebased to get a cleaner history, once it is ready.

This fixes #15742

@rbonichon rbonichon self-assigned this Jun 10, 2024
@svv232
Copy link
Member

svv232 commented Jun 10, 2024

looks interesting so far! i am curious to see how the ledger will eventually be affected

@rbonichon rbonichon force-pushed the rb/account-deletion branch 2 times, most recently from 2c6895a to 41d133e Compare June 24, 2024 08:24
@rbonichon rbonichon changed the base branch from develop to compatible July 16, 2024 14:43
@rbonichon rbonichon changed the title Support for account deletion Support for account deletion in ledgers Jul 16, 2024
@rbonichon rbonichon added this to the Deletable accounts milestone Jul 17, 2024
@rbonichon rbonichon removed this from the Deletable accounts milestone Jul 17, 2024
@rbonichon rbonichon force-pushed the rb/account-deletion branch 5 times, most recently from 8a3abce to 55f09fc Compare July 21, 2024 00:34
dkijania and others added 10 commits July 29, 2024 10:10
…tly_fix_to_develop

Port Fix nightly on master to develop
This reverts commit 25dccfe1bf616e3e2fc70ed5c0f6b3ebd2cbbdc2, reversing
changes made to a801a21.
…_master

[CI][Nightly][Master] Making master nightly green again
…migration_apps_dev

Port remove migration apps from master to develop
…migration_apps

Remove migration apps and jobs from master
It appears we do not need to cache deleted accounts. There is a simpler solution
that checks when calling the parent's location of account whether the returned
value, if any, was actually freed beforehand.
parent -> child signaling needs to check for account equality
This models the behavior of parent_set_notify, that is, the changes are
propagated when the ledgers agree on the account that is touched.
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.

None yet

4 participants