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

Force WritebackCache on #20275

Merged
merged 2 commits into from
Nov 20, 2024
Merged

Force WritebackCache on #20275

merged 2 commits into from
Nov 20, 2024

Conversation

mystenmark
Copy link
Contributor

@mystenmark mystenmark commented Nov 15, 2024

Remove PassthroughCache as an option, but leave the code in place so that nodes currently using it do not break

Copy link

vercel bot commented Nov 15, 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 Nov 20, 2024 10:44pm
3 Skipped Deployments
Name Status Preview Comments Updated (UTC)
multisig-toolkit ⬜️ Ignored (Inspect) Visit Preview Nov 20, 2024 10:44pm
sui-kiosk ⬜️ Ignored (Inspect) Visit Preview Nov 20, 2024 10:44pm
sui-typescript-docs ⬜️ Ignored (Inspect) Visit Preview Nov 20, 2024 10:44pm

@mystenmark mystenmark temporarily deployed to sui-typescript-aws-kms-test-env November 15, 2024 00:41 — with GitHub Actions Inactive
@mystenmark mystenmark changed the title Remove PassthroughCache as an option. (It is still present so that nodes currently using it do not break) Force WritebackCache on Nov 15, 2024
} else {
ExecutionCacheConfigType::WritebackCache
if std::env::var(DISABLE_WRITEBACK_CACHE_ENV_VAR).is_ok() {
error!("DISABLE_WRITEBACK_CACHE is no longer respected. WritebackCache is the default.");
Copy link
Contributor

Choose a reason for hiding this comment

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

should this be fatal?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

i don't think so? i don't think this will affect anyone anyway.


if matches!(
epoch_start_config.execution_cache_type(),
ExecutionCacheConfigType::WritebackCache
Copy link
Contributor

Choose a reason for hiding this comment

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

would it be safer (future proof) to make this an exhuastive match?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

there definitely won't be any new cache types - as soon as I can i will strip all of this conditional stuff out.

@mystenmark mystenmark temporarily deployed to sui-typescript-aws-kms-test-env November 20, 2024 22:43 — with GitHub Actions Inactive
@mystenmark mystenmark merged commit b09b0a8 into main Nov 20, 2024
51 of 52 checks passed
@mystenmark mystenmark deleted the mlogan-remove-proxy-cache branch November 20, 2024 23:15
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.

2 participants