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

[core] cleanup StateAccumulatorV1 #18764

Closed
wants to merge 1 commit into from

Conversation

williampsmith
Copy link
Contributor

Description

Remove v1, leave v2, rename to just StateAccumulator

Test plan

How did you test the new or updated feature?


Release notes

Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.

For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.

  • Protocol:
  • Nodes (Validators and Full nodes):
  • Indexer:
  • JSON-RPC:
  • GraphQL:
  • CLI:
  • Rust SDK:
  • REST API:

Copy link

vercel bot commented Jul 22, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
sui-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Sep 5, 2024 7:34pm
3 Skipped Deployments
Name Status Preview Comments Updated (UTC)
multisig-toolkit ⬜️ Ignored (Inspect) Visit Preview Sep 5, 2024 7:34pm
sui-kiosk ⬜️ Ignored (Inspect) Visit Preview Sep 5, 2024 7:34pm
sui-typescript-docs ⬜️ Ignored (Inspect) Visit Preview Sep 5, 2024 7:34pm

Copy link
Contributor

@mystenmark mystenmark left a comment

Choose a reason for hiding this comment

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

Is there any possibility anyone had this disabled via config? If so, this could break. The safest possible thing is:

  • remove the ability to disable v2 via config
  • then merge this PR after that change has gone out

lastly, it might be worth having an assert that v2 is enabled just in case.

@williampsmith williampsmith force-pushed the william/cleanup-state-accum-v1 branch from 3e36e9c to 8d33916 Compare July 24, 2024 22:12
@williampsmith williampsmith changed the base branch from main to william/make-v1-non-configurable July 24, 2024 22:12
@williampsmith williampsmith marked this pull request as draft July 24, 2024 22:13
Base automatically changed from william/make-v1-non-configurable to main July 24, 2024 22:39
williampsmith added a commit that referenced this pull request Sep 6, 2024
## Description 

We have removed the ability to disable state accumulator v2 previously
by ignoring the config parameter
(#18786), however if a node that
had v2 disabled has been running since before this change without
shutting down, the old config would still be stored in memory. This PR
forces enabling of v2. Once we have reached the epoch change after all
nodes are running this code, we can safely merge
#18764.

## Test plan 

Existing tests

---

## Release notes

Check each box that your changes affect. If none of the boxes relate to
your changes, release notes aren't required.

For each box you select, include information after the relevant heading
that describes the impact of your changes that a user might notice and
any actions they must take to implement updates.

- [ ] Protocol: 
- [ ] Nodes (Validators and Full nodes): 
- [ ] Indexer: 
- [ ] JSON-RPC: 
- [ ] GraphQL: 
- [ ] CLI: 
- [ ] Rust SDK:
- [ ] REST API:
suiwombat pushed a commit that referenced this pull request Sep 16, 2024
## Description 

We have removed the ability to disable state accumulator v2 previously
by ignoring the config parameter
(#18786), however if a node that
had v2 disabled has been running since before this change without
shutting down, the old config would still be stored in memory. This PR
forces enabling of v2. Once we have reached the epoch change after all
nodes are running this code, we can safely merge
#18764.

## Test plan 

Existing tests

---

## Release notes

Check each box that your changes affect. If none of the boxes relate to
your changes, release notes aren't required.

For each box you select, include information after the relevant heading
that describes the impact of your changes that a user might notice and
any actions they must take to implement updates.

- [ ] Protocol: 
- [ ] Nodes (Validators and Full nodes): 
- [ ] Indexer: 
- [ ] JSON-RPC: 
- [ ] GraphQL: 
- [ ] CLI: 
- [ ] Rust SDK:
- [ ] REST API:
@aschran aschran closed this Oct 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants