chore(deps): update dependency ziggycreatures.fusioncache to 2.7.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
ZiggyCreatures.FusionCache	2.7.0 → 2.7.1

---

Release Notes

ZiggyCreatures/FusionCache (ZiggyCreatures.FusionCache)

v2.7.1

🏅 Better Advisor checks

A new check has been added in the Advisor that detecs a potentially incorrect configuration for a System.Text.Json based serializer related to value tuples.

This is not about a FusionCache bug, but about the System.Text.Json serializer's default configuration deviating from the commonly expected one (like, historically, Json.NET for example), see here for more.

Instead of forcing a specific json configuration for FusionCache, the Advisor now checks if the serializer in use is not supporting value tuples correctly and, if so, emits a warning (also configurable) in the logs to warn users about that.

This allows them to make the best decision for their specific use case.

Thanks to @​sychare and @​bassepeder for the hints.

Also, the check for a missing CacheKeyPrefix is now better, more limited in scope.

See here and here for the issues.

🆕 New SerializationConfigIssuesLogLevel option

See the previous item: with this new option is possible to change the desired log level, or suppress it.

🆕 New DistributedLockerErrorsLogLevel option

It's now possible to granularly configure the log level to use for distributed lockers errors, which is nice.

🔭 Better handling of OTEL parent traces

Sometimes the handling of OTEL parent traces was not the best, particularly around highly multithreaded scenarios where a native Activity is not being passed around correctly in the context.

This has now been fixed.

🏷️ OTEL traces for a RemoveByTag(tag) operation now include the tag (duh)

Normally, every operation in the cache has a cache key as the main argument.

In the case of a RemoveByTag(tag) operation though, that is not the case since the main argument is not the cache key, but the tag: strangely enough, FusionCache previously was not logging it front and center, but now it does.

This should help with tagging-related investigations and troubleshootings.

Thanks to community member @​tvardero for spotting this.

See here for the issue.

🐞 Better temporal checks during an L2 to L1 copy

Thanks to community member @​DanielStout5 for spotting this: it's quite rare, but sometimes an entry in L2 may be older than the corresponding entry in L1, and before this fix that assumption did not hold sometimes.
Now an extra check is performed, to make sure that this scenario doesnot produce unwanted results.

See here for the issue.

🐞 Missing operation id with tracing but without a logger

Every single operation in FusionCache has a uniquely identifying operation id (OperationId): this becomes very useful with observability, mainly with logs.

Previously, when no logger was present, the operation id was not generated, at all: this was an optimization to avoid useless work when not actually needed.

But in a case of traces being used without a logger, the traces did not include the operation id for the reason explain above.

With this fix, the optimization is still there, but it also takes into account trace listeners, so that when either a logger or a trace listener is present the operation id is generated, otherwise the optimization is still there.

🔒 Better exception handling for user-initiated cancellations with distributed locking

Community member @​vrbyjimmy discovered a nasty issue with user-initiated cancellations when used with the distributed locker, see the issue for more details.

Than, community member @​qjustfeelitp sent a PR to fix exactly this: teamwork doing its thing, amirite?

Long story short: now that specific OperationCanceledException is being specifically handled to avoid creating issues.

Thanks both!

See here for the issue.

⚠️ Dependencies update to fix in vulnerability in downstream dependencies

Thanks to community member @​SirPustekuchen for noticing that the MessagePack package version being normally used was since marked as vulnerable: now the reference has been updated.

And thanks to communiy membe @​aki-matleb for doing the same, but for the OpenTelemetry.Api package.

See here and here for the issues.

📕 Docs

As always, I took some time to updated the docs with the latest stuff and make them overall better.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• 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.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[MarcelRoozekrans]

Auto-approved by Hermes Renovate cron