Skip to content

Commit 946bf1d

Browse files
deps(core): update dependency ziggycreatures.fusioncache to 2.4.0 (#939)
This PR contains the following updates: | Package | Change | Age | Confidence | |---|---|---|---| | [ZiggyCreatures.FusionCache](https://redirect.github.com/ZiggyCreatures/FusionCache) | `2.3.0` -> `2.4.0` | [![age](https://developer.mend.io/api/mc/badges/age/nuget/ZiggyCreatures.FusionCache/2.4.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/nuget/ZiggyCreatures.FusionCache/2.3.0/2.4.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | --- ### Release Notes <details> <summary>ZiggyCreatures/FusionCache (ZiggyCreatures.FusionCache)</summary> ### [`v2.4.0`](https://redirect.github.com/ZiggyCreatures/FusionCache/releases/tag/v2.4.0) #### 🏷️ Add `StaleTags` to factory execution context Community user [@&#8203;ted-mundy](https://redirect.github.com/ted-mundy) noticed a tricky behavior when using Tagging with stale entries (see next point). To solve it, I added a new `StaleTags` property to the factory execution context, so that now it's possible to access both the tags that are being passed to the `GetOrSet()` call and the existing tags of the stale entry in the cache (if any), like this: ```c# cache.GetOrSet<string>( "foo", (ctx, token) => { // THE TAGS PASSED BELOW ("tag1", "tag2" and "tag3") ctx.Tags; // THE TAGS OF THE STALE ENTRY ALREADY IN THE CACHE, IF ANY ctx.StaleTags; return "Combo"; }, tags: ["tag1", "tag2", "tag3"] ); ``` This can be useful even in other scenarios, like applying some custom logic about what to do based on the tags already in the cache. Nice. #### 🐞 Fix for tags with stale entries As mentioned above, community user [@&#8203;ted-mundy](https://redirect.github.com/ted-mundy) noticed a tricky behavior when using Tagging with stale entries. Thanks to the addition of the new `StaleTags` property, this is now solved for good. Thanks [@&#8203;ted-mundy](https://redirect.github.com/ted-mundy) ! See [here](https://redirect.github.com/ZiggyCreatures/FusionCache/issues/515) for the original issue. #### Ⓜ️ Better entry options mapping with HybridCache adapter Community user [@&#8203;TheSpookyElectric](https://redirect.github.com/TheSpookyElectric) noticed that, when working with the [HybridCache](https://redirect.github.com/ZiggyCreatures/FusionCache/blob/main/docs/MicrosoftHybridCache.md) adapter, the `LocalCacheExpiration` was not being handled correctly in all cases. The mapping logic has been updated to account for that, and it now works as expected. Thanks [@&#8203;TheSpookyElectric](https://redirect.github.com/TheSpookyElectric) ! See [here](https://redirect.github.com/ZiggyCreatures/FusionCache/issues/498) for the original issue. #### 🐞 Fix for `WithRegisteredSerializer()` Community user [@&#8203;Inok](https://redirect.github.com/Inok) noticed something... strange. The [builder](https://redirect.github.com/ZiggyCreatures/FusionCache/blob/main/docs/DependencyInjection.md#%EF%B8%8F-builder), when calling `WithRegisteredSerializer()` on it, was doing something else: acting on the distributed cache. That was, well... dumb, that's just what it was: my bad. Now this has been solved. Thanks [@&#8203;Inok](https://redirect.github.com/Inok) ! See [here](https://redirect.github.com/ZiggyCreatures/FusionCache/issues/509) for the original issue. #### 🐞 Fix for `InvalidOperationException` when using `AlwaysOffSampler` with OTEL Community user [@&#8203;DFSko](https://redirect.github.com/DFSko) noticed an `InvalidOperationException` being thrown when working with OTEL and using the `AlwaysOffSampler`: this had to do with setting the current `Activity` after certain operations, in conjunction with activities with a state not compatible for being set as the current one. This has now been solved. Thanks [@&#8203;DFSko](https://redirect.github.com/DFSko) ! See [here](https://redirect.github.com/ZiggyCreatures/FusionCache/issues/501) for the original issue. #### 📕 Fix for an inline doc issue Community user [@&#8203;marcominerva](https://redirect.github.com/marcominerva) discovered a wrong description for the `WithDistributedCache()` method on the builder: fixed. Thanks [@&#8203;marcominerva](https://redirect.github.com/marcominerva) ! See [here](https://redirect.github.com/ZiggyCreatures/FusionCache/issues/496) for the original issue. #### ✅ 1500 tests, huzza! FusionCache reached 1500 tests: <img width="774" height="151" alt="image" src="https://github.com/user-attachments/assets/bc2d5e87-ca32-49ff-a399-2e4969e4b80d" /> That's it, that's the tweet 🙂 </details> --- ### Configuration 📅 **Schedule**: Branch creation - "after 9pm,before 6am" in timezone Europe/Zurich, Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/dotnet/dotnet-operator-sdk). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS43MS4xIiwidXBkYXRlZEluVmVyIjoiNDEuNzEuMSIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiZGVwZW5kZW5jaWVzIl19--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
1 parent 54b0cd7 commit 946bf1d

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/KubeOps.Abstractions/KubeOps.Abstractions.csproj

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@
1717
<PackageReference Include="JsonPatch.Net" Version="3.3.0" />
1818
<PackageReference Include="KubernetesClient" Version="17.0.4" />
1919
<PackageReference Include="Microsoft.Extensions.Hosting.Abstractions" Version="9.0.8"/>
20-
<PackageReference Include="ZiggyCreatures.FusionCache" Version="2.3.0" />
20+
<PackageReference Include="ZiggyCreatures.FusionCache" Version="2.4.0" />
2121
</ItemGroup>
2222

2323
</Project>

0 commit comments

Comments
 (0)