failure to: write to a file in a loop on machine1; tail -f on machine2;
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
My experience was that at first tail -f showed the stale file, and then I got input/output error
my log id: ceb3ebd4dd0aff0c7b550a1c [from machine2]
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
No source file or test is named. Start by reviewing the KBFS file-sync and filesystem entry points related to writing a file on machine1 and following it with tail -f on machine2, then reproduce the stale-file and input/output error using log id ceb3ebd4dd0aff0c7b550a1c; done means identifying the failure and adding a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100