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

feat: allow files rm --force #2205

Open
1 task
SgtPooki opened this issue Feb 5, 2024 · 0 comments
Open
1 task

feat: allow files rm --force #2205

SgtPooki opened this issue Feb 5, 2024 · 0 comments
Labels
need/triage Needs initial labeling and prioritization

Comments

@SgtPooki
Copy link
Member

SgtPooki commented Feb 5, 2024

Is your feature request related to a problem? Please describe.
It's possible for users to get into a state where they have non-unixfs files in MFS, which will result in errors like Error: unrecognized node type in cache node.

When non-unixfs files are in MFS, removal of those files will fail in webui without error.

They also fail to be removed in the command line unless rm --force is used.

Describe the solution you'd like
When a user attempts to remove a file, we should provide an option to "force" remove the file.

Describe alternatives you've considered

We may also want to enable a fallback prompt to "force" remove files when a user attempts to remove a file and it fails.

Additional context

We should also prevent users from adding/importing non-unixfs files via the webui (I believe I added the files that got me into this state via the webui)

Code that needs updated

Related issues

Tasks

Preview Give feedback
@SgtPooki SgtPooki added the need/triage Needs initial labeling and prioritization label Feb 5, 2024
@github-project-automation github-project-automation bot moved this to Needs Grooming in IPFS-GUI (PL EngRes) Feb 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
need/triage Needs initial labeling and prioritization
Projects
No open projects
Status: Needs Grooming
Development

No branches or pull requests

1 participant