On the market info page, the acquisition table does not update when a processed SSE event arrives. The user has to manually reload to see the new acquisitions.
Steps to reproduce
Open the market info page for a type.
Trigger processing that produces new acquisitions (so a processed SSE event fires).
Expected
The acquisition table refreshes to reflect the newly processed acquisitions.
Actual
The table stays stale; a manual reload is needed to see the updates.
## Summary
On the market info page, the acquisition table does not update when a `processed` SSE event arrives. The user has to manually reload to see the new acquisitions.
## Steps to reproduce
1. Open the market info page for a type.
2. Trigger processing that produces new acquisitions (so a `processed` SSE event fires).
## Expected
The acquisition table refreshes to reflect the newly processed acquisitions.
## Actual
The table stays stale; a manual reload is needed to see the updates.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
On the market info page, the acquisition table does not update when a
processedSSE event arrives. The user has to manually reload to see the new acquisitions.Steps to reproduce
processedSSE event fires).Expected
The acquisition table refreshes to reflect the newly processed acquisitions.
Actual
The table stays stale; a manual reload is needed to see the updates.