-
Notifications
You must be signed in to change notification settings - Fork 11.2k
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
Force WritebackCache on #20275
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
3 Skipped Deployments
|
} 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."); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should this be fatal?
There was a problem hiding this comment.
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 |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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.
…des currently using it do not break)
6d6dc2a
to
59b8d2f
Compare
Remove PassthroughCache as an option, but leave the code in place so that nodes currently using it do not break