keybase / keybase/client

keybase fs cp -f [SOURCE] [DEST] — the force flag doesn't work anymore

Open
#24,219 6 comments 5 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
9.2k
Forks
1.3k
Avg merge
12h 58m
Merged PRs (30d)
56

Description

> Note, the kbfs repo is mysteriously archived now, so ... I am filing this here.

It's been broken for a bit now, but if `somefile` already exists at the destination, it fails to copy even if `-f` is used:
```
[myusername@blahblahblah ~]$ keybase fs cp -f ./tmp/somefile /keybase/private/myusername/
▶ ERROR name exists (code 5101)
```

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the `keybase fs cp -f ./tmp/somefile /keybase/private/myusername/` command and trace the `keybase fs cp` entry point handling the force flag. Confirm the behavior with an existing destination; done means the command replaces the existing destination instead of returning the `name exists` error.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.