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

all: Make graphman chain call-cache remove safer #4397

Merged
merged 1 commit into from
Feb 24, 2023

Conversation

lutter
Copy link
Collaborator

@lutter lutter commented Feb 24, 2023

The command defaulted to the dangerous operation of clearing the entire cache. Now, the entire cache can only be cleared by passing the annoyingly named --remove-entire-cache.

In a similar vein, it used to be ok to omit --from or --to which would default to the first or last block. They now need to both be specified to make the user be clearer about how much of the call cache they are going to remove.

@lutter lutter requested a review from tilacog February 24, 2023 01:30
The command defaulted to the dangerous operation of clearing the entire
cache. Now, the entire cache can only be cleared by passing the annoyingly
named `--remove-entire-cache`.

In a similar vein, it used to be ok to omit --from or --to which would
default to the first or last block. They now need to both be specified to
make the user be clearer about how much of the call cache they are going to
remove.
Copy link
Contributor

@tilacog tilacog left a comment

Choose a reason for hiding this comment

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

👍

@lutter lutter merged commit 4fb2cc6 into master Feb 24, 2023
@lutter lutter deleted the lutter/remove-call-cache branch February 24, 2023 17:12
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.

None yet

2 participants