TTL on objects converts seconds to milliseconds

[nightroman]

Describe the bug

Getting TTL on objects (Hash, List, Set) seemingly converts seconds to milliseconds.

Steps to reproduce the bug

Use the below code snippet or the attached console app project:
GarnetIssue2.zip

using StackExchange.Redis;

using var redis = ConnectionMultiplexer.Connect("127.0.0.1:3278");
var db = redis.GetDatabase();

var key = "test:issue";

// KeyExpire on String - OK
db.KeyDelete(key);
db.StringSet(key, "a");
db.KeyExpire(key, TimeSpan.FromSeconds(10));
var ttlString = db.KeyTimeToLive(key);

// KeyExpire on Hash - NOT OK
db.KeyDelete(key);
db.HashSet(key, "a", "b");
db.KeyExpire(key, TimeSpan.FromSeconds(10));
var ttlHash = db.KeyTimeToLive(key);

// Results:
Console.WriteLine($"TTL String : {ttlString}");
Console.WriteLine($"TTL Hash   : {ttlHash}");

Output:

TTL String : 00:00:09.9980000
TTL Hash   : 00:00:00.0090000

Expected behavior

Result TTL should be approximately the same for String and Hash, about 10 seconds.

Actual results: ~10 seconds for String and ~9 milliseconds for Hash.

Tested List and Set types also show the issue.

Additional context

• Garnet 1.0.6
• StackExchange.Redis 2.7.33
• Windows 11