Skip to content

fix(events): Don't Cache Simulated Events (#2672)#3014

Merged
ebiggz merged 3 commits intocrowbartools:v5from
phroggster:fix/2672
Mar 10, 2025
Merged

fix(events): Don't Cache Simulated Events (#2672)#3014
ebiggz merged 3 commits intocrowbartools:v5from
phroggster:fix/2672

Conversation

@phroggster
Copy link
Collaborator

@phroggster phroggster commented Feb 22, 2025

Description of the Change

  • Revert feat: allow simulated events to force run #1889
    • Removes the "Force event to run" checkbox in the Simulate Event modal.
  • Disable event caching for simulated events.
    • This impacts only simulation of: follow, raid, reward redemption, and viewer arrived event types. Nothing else was using the event cache (in core).

Applicable Issues

#2672
#1782

Testing

Minimal (it works), but I need to submit this first and rouse some troops together for more depth and breadth of testing.
Live events and simulated events behave appropriately. Follow/unfollow/follow (and raid) spam hits the caching layer (one event gets through per 12 hrs), before and/or after a simulation with the same data.

Screenshots

New (old) simulate dialog:
2672

Log of simulating two raids from the same user in quick succession:
2672-multi-simulate-log

This reverts commit b8ef5b4.

Signed-off-by: phroggster <phroggster@users.noreply.github.com>
- Simulating an event trigger which had caching enabled would inhibit
  later de-facto triggerings of that event, at least until the event
  expired from the cache (12 hrs +/- 10 min).
- Raid, follow, reward redemptions, and viewer arrived events for a
  particular user name would therefore be unusable for 12 hrs.
- Yes, you could force simulate them, but not actually receive them.
- Adjust to having event simulations ignore the cache.
- ref crowbartools#2672, crowbartools#1782
@phroggster phroggster requested a review from ebiggz as a code owner February 22, 2025 04:39
@ebiggz ebiggz merged commit a4a91c8 into crowbartools:v5 Mar 10, 2025
1 check passed
@phroggster phroggster deleted the fix/2672 branch March 10, 2025 07:26
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