microsoft / microsoft/p4vfs

How can i sync?

Open
#13 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
308
Forks
20
Avg merge
14h 56m
Merged PRs (30d)
1

Description

I opened the CMD with administrator. Then i set the $P4PORT, $P4CLIENT and $P4USER variable. I run the p4vfs.exe login command and then login to the perforce with password.
I want to sync my debot with p4vfs.exe sync //myprojects/projectname/username/folder/name/... command.
But the p4vfs always crash with sync action:

P4VFS version 1.24.2.0
Virtual Sync: ["//myprojects/projectname/username/folder/name/..."] Normal Atomic @999999
Started at [03/24/2023-17:24:52] version [1.24.2.0]
1 Modification messages to act on.
Unsupported sync action: None <--- ERROR
Virtual Sync Summary:
Total Files: 1 / 1
Total Time: 0 sec (0.656)
Virtual Mod Time: 0 sec
Resident Mod Time: 0 sec
Virtual File Size: 0 bytes
Disk File Size: 0 bytes

and here is my p4vfs.exe info output:
P4VFS version 1.24.2.0
P4 UserName: username
P4 ClientName: p4vfs
P4 ClientHost: DESKTOP999999
P4 ClientRoot: c:\Share
P4 ClientStream:
P4 ServerAddress: perforceip:1999
P4 ServerVersion: P4D/LINUX26X86_64/2021.1/2313999 (2022/07/15)
P4 CaseHandling: sensitive
P4VFS CurrentVersion: 1.24.2.0
P4VFS ServiceVersion: 1.24.2.0
P4VFS DriverVersion: 1.24.0.0
P4VFS DriverReady: True
P4VFS ServiceReady: True
P4VFS SystemReady: True

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 by reproducing the reported p4vfs.exe sync command after login, using the supplied P4VFS info output as the environment reference. Investigate the “Unsupported sync action: None” message and the resulting crash; done means the command no longer crashes or the issue is documented with a confirmed cause and supported usage.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.