Keybase desktop app made 56GB of disk writes in a 36hr runtime period
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
For details, see the discussion on keybasefriends#general on 2019-12-03.
my log id: e6c623c424df580d38dfc01c
excerpted Timeline of process writes:
- 57GB: 2019-12-03 6:30pm
- 63GB: 2019-12-03 7:30pm
- 89GB: 2019-12-04 10:00am
- 109.5GB: 2019-12-04 12:30am
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the keybasefriends#general discussion from 2019-12-03 and the supplied log id e6c623c424df580d38dfc01c. Review the process-write timeline to identify the source of the excessive disk activity; done means the cause is established and a way to verify that the writes no longer recur is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100