Skip to content

Deprecating --hard option in network clean command #2849

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

Merged
merged 1 commit into from
Jun 12, 2025

Conversation

Tonix517
Copy link
Collaborator

@Tonix517 Tonix517 commented Jun 11, 2025

Why this should be merged

to address #2784 (comment)

How this works

How this was tested

How is this documented

@Tonix517 Tonix517 force-pushed the tonyz/deprecate_clean_hard branch from 5792f94 to b87d6fb Compare June 11, 2025 23:22
@Tonix517 Tonix517 marked this pull request as ready for review June 11, 2025 23:54
@Tonix517 Tonix517 requested a review from a team as a code owner June 11, 2025 23:54
@Tonix517 Tonix517 changed the title Deprecating --hard option in clean command Deprecating --hard option in network clean command Jun 12, 2025
@sukantoraymond
Copy link
Collaborator

Screenshot 2025-06-12 at 4 16 07 PM
So clean network -- hard will actually remove the entire bin directory. It contains all the binaries listed above. Why do we want to delete hard option? @felipemadero

}
ux.Logger.PrintToUser("removing all downloaded avalanchego and plugin binaries")
binDir := filepath.Join(app.GetBaseDir(), constants.AvalancheCliBinDir)
cleanBins(binDir)
Copy link
Collaborator

Choose a reason for hiding this comment

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

I mean, we don't even need this functionality just don;t do it. Lets keep the downloaded binaries after a clean.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

removed this block

@@ -117,7 +117,7 @@ var _ = ginkgo.Describe("[Network]", ginkgo.Ordered, func() {
commands.DeleteSubnetConfig(subnetName)
})

ginkgo.It("clean hard deletes plugin binaries non SOV", func() {
ginkgo.It("clean deletes plugin binaries non SOV", func() {
Copy link
Collaborator

Choose a reason for hiding this comment

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

we don't need this one, if we are not removing binaries anymore

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

removed

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

to confirm: do we want to do ResetPluginsDir anyway at clean?

@felipemadero
Copy link
Collaborator

Screenshot 2025-06-12 at 4 16 07 PM So clean network -- hard will actually remove the entire bin directory. It contains all the binaries listed above. Why do we want to delete hard option? @felipemadero

we don't want to continue deleted this, I also made the same comment in parallel

@Tonix517 Tonix517 force-pushed the tonyz/deprecate_clean_hard branch from b87d6fb to 7f788b8 Compare June 12, 2025 20:46
@Tonix517 Tonix517 requested a review from felipemadero June 12, 2025 20:47
Copy link
Collaborator

@felipemadero felipemadero left a comment

Choose a reason for hiding this comment

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

LGTM but needs to pass CI

@Tonix517 Tonix517 force-pushed the tonyz/deprecate_clean_hard branch 2 times, most recently from 8523b89 to 298ff2e Compare June 12, 2025 21:40
@Tonix517 Tonix517 force-pushed the tonyz/deprecate_clean_hard branch from 298ff2e to d3e9210 Compare June 12, 2025 21:51
@Tonix517 Tonix517 merged commit e93cee2 into main Jun 12, 2025
53 checks passed
@Tonix517 Tonix517 deleted the tonyz/deprecate_clean_hard branch June 12, 2025 22:20
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