microsoft / microsoft/Windows-classic-samples

[Cloud Mirror] CF_CALLBACK_TYPE_FETCH_PLACEHOLDERS called multiple times

Open
#284 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
5.7k
Forks
3.3k
PR merge metrics
No merged PRs in 30d

Description

I'm trying to modify the Cloud Mirror sample to implement on demand population. I registered a new callback for type CF_CALLBACK_TYPE_FETCH_PLACEHOLDERS, changed the Population Policy to Full when registering the sync root folder and removed the creation of placeholders at initialization. What happens is that the new callback is called several times at the point to degrade Explore's performance, while it should be called only once per directory visited.

I found the same bug reported in stack overflow, but without any solution so I decided to report it here as well
https://stackoverflow.com/questions/63348568/cfapi-cf-callback-type-fetch-placeholders-calls-back-repeatedly

The author of this post even created a fork with the changes to reproduce the problem, which can be found here
https://github.com/legsak1mbo/VCCloudMirror/

I believe it is not based on the latest commit but I'm using the latest and the problem is still there. I can create a fork with my changes if needed.

I appreciate any help. Thanks

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 Cloud Mirror sample and the CF_CALLBACK_TYPE_FETCH_PLACEHOLDERS registration and Population Policy described in the report. Reproduce the repeated callbacks while visiting a directory, then compare the behavior with the linked Stack Overflow report and VCCloudMirror fork; done means the callback behavior matches the stated once-per-directory expectation.

Written by the indexing model from the issue text.

Assessment

Domain
cloud, desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.