[backport v2.8.next1] Steve socket is spammed on fresh visit to a resource detail page #10566
Labels
area/performance
kind/bug
priority/0
QA/manual-test
Indicates issue requires manually testing
size/0.5
Size Estimate 0.5
Milestone
This is a backport issue for #10540, automatically created via GitHub Actions workflow initiated by @richard-cox
Original issue body:
We should tackle this after fix for rancher/rancher#41809 has merged
Setup
Describe the bug
After visiting by url / refreshing on an oldish steve based resource's detail page the steve socket gets spammed with messages.
This probably applies to the resource's edit page as well.
revision
. We watch for changes for that set of resource over web socket using the revision as a starting pointrevision
is too old we should get a resource.errortoo old
messagetoo old
message was not provided and will be / has been fixed via [SURE-7122] Excessive WebSocket activity when watching resources with permission by name rancher#41809too old
handlingtoo old
--> http request for single resource & use revision from within forever cycleTo Reproduce
Result
too old
messages as the ui tries to watch with the old revision AND http requests with a bad url (no ns)Expected Result
The text was updated successfully, but these errors were encountered: