[Bug]: vacuum() does not clean ::result hash

[levish0]

What happened?

done_job.lua stores job results in {namespace}:data::result hash on every job completion, but vacuum.lua never cleans these entries. The result hash grows indefinitely.

Expected behavior

vacuum() should also remove result hash entries for vacuumed jobs, or there should be a TTL/cleanup mechanism for results.

Steps to reproduce

1. Run jobs that complete successfully
2. Call storage.vacuum().await
3. Check Redis: HLEN {namespace}:data::result
4. Count remains the same - results are not cleaned

Minimal code example

let mut storage: RedisStorage<MyJob> = RedisStorage::new(conn);

// Push and complete jobs
storage.push(MyJob { ... }).await?;
// ... jobs complete ...

// Vacuum
storage.vacuum().await?;

// Result hash still has entries
// redis-cli: HLEN "my_job:data::result" → still shows count

Version

0.7.x

Environment

• OS: Windows 11
• Rust version: 1.91.1
• Cargo version: 1.91.1

Relevant log output

Additional context

done_job.lua line 5:

redis.call("hmset", KEYS[3].. ns, ARGV[1], ARGV[3])

vacuum.lua only cleans KEYS[1] (done_list) and KEYS[2] (data hash).
KEYS[3]::result is never touched.

[geofmureithi]

Thanks for reporting this issue. Unfortunately this is a tricky one to solve for 0.7.x as the repos have been split. I think we can ensure it is fixed in the 1.0 next beta release. I will get back on this with more information or a a patch.

[geofmureithi]

I think this can be backported for a 0.7.5 release