Redis [BUG] TS.INFO causes __redis__:invalidate

Describe the bug

TS.INFO causes redis:invalidate while no data is changed. This also happens when it is called for a non-existing key.

To reproduce

Open 2 terminals with redis-cli, In the 1st check the ID with CLIENT INFO and then SUBSCRIBE __redis__:invalidate. In the 2nd enable tracking for the ID in the step above CLIENT TRACKING ON REDIRECT 16 BCAST. Then execute TS.INFO a. The 1st terminal will receive 1) "message" 2) "__redis__:invalidate" 3) 1) "a" Expected behavior

invalidate messages should only be received when data respective to that key changes

Comment From: sundb

@nunojpg Please create a new issue in https://github.com/RedisTimeSeries/RedisTimeSeries. although TS.INFO is a readonly command, but it uses RedisModule_OpenKey with REDISMODULE_WRITE, so you can get the invalidate message.

ref code: https://github.com/RedisTimeSeries/RedisTimeSeries/blob/2ef0d43c353d36b2b327120409d32f84d3748b0f/src/module.c#L55 https://github.com/RedisTimeSeries/RedisTimeSeries/blob/2ef0d43c353d36b2b327120409d32f84d3748b0f/src/tsdb.c#L79