[cosmin-staicu]

Summary

On the Redis Pub/Sub transport a node also receives the messages it publishes, and decoded each one in full (System.Text.Json) before dropping its own. Formatters can now read only the event source from the payload, so a node's own message is dropped without a decode. The message format does not change.

 OnMessage(payload)
+  formatter has a source matcher and it says "from this node" -> drop, no decode
   decode -> SameSource? drop : apply                            // unchanged otherwise

• New public interfaces in Abstractions: IEventSourceMatcherProvider.CreateSourceMatcher(Uri) builds a matcher once per subscriber; IEventSourceMatcher.IsFromSource(ReadOnlyMemory<byte>) checks one payload.
• CacheEventFormatter implements it (Source); the CloudEvents formatter implements it when it wraps a JSON formatter (source). Both use one Utf8JsonReader-based matcher that compares with ValueTextEquals (JSON escapes handled) and allocates nothing.
• A message counts as own only when the decode would drop it: a case-only difference, a missing or repeated source, or malformed JSON still goes through decode and SameSource. Custom formatters without the capability keep decode-then-compare.
• Messages are still decoded while Debug or Trace logging is on, so the own-message logs keep the event id.
• GetOrAddResultRedisIntegrationTests.A_redis_hit_allocates_about_what_get_or_add_does moves to a new non-parallel RedisAllocation collection with the same Redis fixture, so its allocation count no longer includes other tests running in parallel.

Evidence

1000 own messages: 1751 -> 0 bytes per own message.

37 new cases: own skipped with 0 decodes, foreign applied, escaped, non-ASCII and case-only sources, Source after Data or missing, custom formatter, CloudEvents, allocation probe. net10.0 4364 passed, net8.0 4322 passed; the moved test passed 6/6 full runs.

Merge Danger

Door: two-way; the wire format is unchanged.

Blast Radius: Pub/Sub readers. An own message that is itself malformed no longer logs the "Event invalid" warning when Debug and Trace are off. The CloudEvents formatter test-decodes a sample payload once per subscriber when the topic is created.

[github-actions]

🔎 Maintainer heads-up: automated triage flagged this PR as potentially material, so it may need a signed CLA in addition to the DCO sign-off.

Strong signals

• adds public API surface (PublicAPI.Unshipped.txt in src/UiPath.Caching.Abstractions, src/UiPath.Caching.CloudEvents, src/UiPath.Caching)

This is advisory only — the bot does not decide. Please judge against the CLA criteria (material, product-critical, patent-sensitive, corporate contributor, broad commercial use). Note that thresholds can be gamed by splitting PRs, so use your judgement.

• If a CLA is needed → add the cla-required label (a contributor comment with signing steps is posted automatically).
• If it is not needed → replace needs-cla-review with cla-not-required so later pushes don't re-flag it.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
95.8% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud