Running Watch command after closing first one doesn't work

[Abhijeetsng97]

Steps to reproduce: open 2 dice db cli in one cli at every interval keep on doing GET key in another cli stop a watch CMD and start agin it stops receving updates

fix PR: https://github.com/DiceDB/dicedb-cli/pull/41 https://github.com/DiceDB/dicedb-go/pull/13

after fix:

[mintobit]

Is this still reproducible? We changed implementation of client-server communication, might have fixed it accidentally

[Abhijeetsng97]

Hey will check and update I saw many changes in dicedb-go If any issue is there will push a fix

[Abhijeetsng97]

@mintobit @arpitbbhayani This issue isn't fixed with lastest changes in dicedb-go I raised a pr with changes but it had conflict https://github.com/DiceDB/dicedb-go/pull/13 Will raise another one in couple of days

Issue was mainly setting a read timeout while reading from TCP connection and handling of cancel in go channel

[Kaushal-26]

@Abhijeetsng97 I also got this issue, let me know if I can pick this up if you haven't started it

[Aditya-ds-1806]

@mintobit I maintain dicedb-driver, js client for DiceDB, and can confirm this still exists, I had reported this issue in #1665 a few weeks back. This bug has been there from a long time and continues to exist even after the new protocol changes. My current workaround has been to skip the handshake entirely for watchable connections. https://github.com/Aditya-ds-1806/dicedb-driver/blob/d362583029ff7c2a5c0e91c99e6987fe08f6b6cd/lib/DiceDBSocket.ts#L260-L268