How does p4vfs work with P4 Client correctly
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 308
- Forks
- 20
- Avg merge
- 14h 56m
- Merged PRs (30d)
- 1
Description
When I Installed p4vfs service, and rehydrating some files, their size becomes 0, but it seems that just a refresh operation from the p4 client will trigger IO to read the complete file, causing these files to be re-downloaded. How can I correctly cooperate with the P4 client to avoid unexpected dewatering?
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 files, tests, or entry points are identified. Start by reproducing the sequence with the p4vfs service, a rehydrated file, and a P4 client refresh, then trace the file hydration and dewatering behavior. Done means the correct P4 client interaction is documented or the unexpected re-download is prevented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100