FileCachingLayer does not restore the saved data file even if the application is restarted. Manifest file empty.

What does the bug do?

Although it saves the json file of the data generated with FileCachingLayer (JsonFileCacheLayer) in the folder, it does not write its metadata to the manifest file. When the application is restarted, although the data file exists, it does not pull the cached data and calls it from the getter again.

How can it be reproduced?

// Startup.cs
services.AddCacheStack(
   new ICacheLayer[]
   {
       //new MemoryCacheLayer(),
       new JsonFileCacheLayer(@"D:\jsoncachelayer")
   },
    new[] {
        new AutoCleanupExtension(TimeSpan.FromMinutes(30))
    });

// Controller.cs
public async Task<IActionResult> IndexAsync()
{
    var model = await _cacheStack.GetOrSetAsync<IndexViewModel>($"indexviewmodel", async (old) =>
    {
        return await _lnwCache.GetHomepageIndexModel();
    }, new CacheSettings(TimeSpan.FromMinutes(15)));

    return View("Index", model);
}

// manifest.json
{"Value":{}}

The file containing the data is stored in the folder named A1303B032BB63284F6F595600591AA13.json. But the manifest file is empty.

P.S: Read and write permissions are defined to the folder.

• NuGet Package Version: 0.11.2
• .NET Runtime Version: .NET 5
• Operating System: Windows 10

[Turnerj]

Yep, the DI system had this as intended behaviour so Cache Tower was just using it wrong. I’ve updated the service collection extensions to resolve this issue (allowing the cache stack and its layers to dispose, allowing the manifest to save).

I’ve just released v0.11.3 which includes the fix to the service collection/dependency injection so it should be disposed now (and thus trigger the manifest to save).

Let me know if it is still a problem after you’ve updated!

[Turnerj]

Everything is fine and working properly. Thank you for your effort.

Glad it is all working now!

There is one more thing I am wondering about. Is it possible to make a function that can manually refresh the data in the background? Same as with the staleAfter parameter but manually. cacheStack.RefreshValue(key, function?);

That’s an interesting idea - I’ve created #189 to track it. From what I’m picturing at the moment, it will likely need to take in the time-to-live value otherwise it can’t save the refreshed value in the cache. The method will likely need to be async too as background refreshing kinda cheats by simply not awaiting internally on an action.