keybase / keybase/client

Gracefully shutdown kbfs when still writing files

Open
#14,281 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
9.2k
Forks
1.3k
Avg merge
12h 58m
Merged PRs (30d)
56

Description

Hi
We are using kbfsfuse to store secrete during a ci-pipeline. This works mostly excellent so thanx for the great stuff
However sometimes we write stuff and than the last secret stored is likely to get lost since the process is killed before kbfs has the time to complete the update.
I have the basic feeling that keybase ctl stop should be able to help me here. I could first use this to stop the process and than keep the script alive until I have verified that the kbfs process is gone. however. keybase ctl stop does not work and ends up in a loop.

my log id: 7456cde138762f3b40a8e61c

A second note,.. even though it feel keybase ctl stop should store data before it kills kbfs when I test this with echo "my test" > /keybase/public/aaldert/test && keybase ctl stop No file is created

Again thnx for the cool stuff. Let me know if I can help with more info

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the keybase ctl stop entry point and reproduce the kbfsfuse shutdown while a file write is still pending. Check the reported loop and whether echo "my test" > /keybase/public/aaldert/test && keybase ctl stop preserves the file; done means shutdown exits cleanly and the final write is stored.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.