Skip to content

Conversation

@stefanceriu
Copy link
Member

This will allow the NSE process to populate the event cache store with even data after retrieving it from sync, as opposed to dropping after rendering the notification it as it did previously.

…a stores instead of in-memory ones

This will allow the NSE process to populate the event cache store with even data after retrieving it from sync, as opposed to dropping after rendering the notification it as it did previously.
@codecov
Copy link

codecov bot commented Dec 8, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 88.50%. Comparing base (238e4e8) to head (e377d58).
⚠️ Report is 5 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #5934   +/-   ##
=======================================
  Coverage   88.50%   88.50%           
=======================================
  Files         362      362           
  Lines      103291   103293    +2     
  Branches   103291   103293    +2     
=======================================
+ Hits        91413    91415    +2     
- Misses       7535     7536    +1     
+ Partials     4343     4342    -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@codspeed-hq
Copy link

codspeed-hq bot commented Dec 8, 2025

CodSpeed Performance Report

Merging #5934 will not alter performance

Comparing stefan/notificationClientCrossProcessLockingStores (e377d58) with main (8637bdc)

Summary

✅ 50 untouched

@stefanceriu stefanceriu requested a review from Hywan December 8, 2025 11:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants