dry-autumn-33122
05/27/2025, 8:29 PMbetter-park-34863
05/27/2025, 9:01 PMnpm start which always used to auto refresh.wooden-umbrella-84098
05/27/2025, 10:29 PMstart script in package.jsonfreezing-spoon-14104
05/28/2025, 12:25 PMbetter-park-34863
05/28/2025, 12:32 PMwooden-umbrella-84098
05/28/2025, 12:32 PMcame with the downside of always loading until agent finishedWe definitely need to fix this ASAP--we shouldn't have checked in that regression
wooden-umbrella-84098
05/28/2025, 12:33 PMfreezing-spoon-14104
05/28/2025, 12:34 PMWe definitely need to fix this ASAP--we shouldn't have checked in that regressionSorry, I should have made the consequence clearer 😓 There is an alternative I can push ASAP, but not 100% reliable
wooden-umbrella-84098
05/28/2025, 12:35 PMwooden-umbrella-84098
05/28/2025, 12:36 PMfreezing-spoon-14104
05/28/2025, 12:39 PMinvalidateQuery that would trigger a refetch on file changes. That caused a serious issue where loading existing conversations would call that method on every file change, and trigger a new request as well, causing a huge burst of these calls and possibly self-DOSing
The change was to use removeQuery instead, that clears all cache and does not request a refetch.freezing-spoon-14104
05/28/2025, 12:39 PMwooden-umbrella-84098
05/28/2025, 12:41 PMfreezing-spoon-14104
05/28/2025, 12:42 PMcancelRefetch option where I'd pass the boolean value that determines whether we're receiving messages at a high rate (the same value that determines whether we display the messages or wait for them to finish loading)freezing-spoon-14104
05/28/2025, 12:43 PMwooden-umbrella-84098
05/28/2025, 12:45 PMfreezing-spoon-14104
05/28/2025, 12:59 PM