Read-repair behaviour for outdated commands no longer works #7818
Description
Description
Previously, if you used a command that your client had cached shortly after that command was updated, the client would error once, then fix the local cache for your next use. This behaviour no longer works and requires a client restart every time.
Steps to Reproduce
- Have your client cache a command
- Update that command
- Try to use the now-outdated cached version twice
Expected Behavior
Read-repair functionality should kick in and sync the local cache with the updated version of the command
Current Behavior
It keeps erroring without updating the cache, requiring a client restart every time
Screenshots/Videos
No response
Client and System Information
Unlikely to be version-specific as this has been occurring for months on many different versions