ENOENT: no such file or directory

[yovanoc]

since the fix of #93 I got this now

{
  err: {
    filePath: '/home/user/.app/cache/data/version1.0.0/123',
    error: Error: ENOENT: no such file or directory, open '/home/user/.app/cache/data/version1.0.0/123'
        at async open (node:internal/fs/promises:641:25)
        at async readFile (node:internal/fs/promises:1279:14)
        at async deleteFileIfExpired (file:///app/node_modules/.pnpm/bentocache@1.5.1_ioredis@5.8.2/node_modules/bentocache/build/chunk-UWZXJRIZ.js:6:21)
        at async pruneExpiredFiles (file:///app/node_modules/.pnpm/bentocache@1.5.1_ioredis@5.8.2/node_modules/bentocache/build/chunk-UWZXJRIZ.js:27:5)
        at async prune (file:///app/node_modules/.pnpm/bentocache@1.5.1_ioredis@5.8.2/node_modules/bentocache/build/src/drivers/file/cleaner_worker.js:10:3)
        at async Timeout._onTimeout (file:///app/node_modules/.pnpm/bentocache@1.5.1_ioredis@5.8.2/node_modules/bentocache/build/src/drivers/file/cleaner_worker.js:17:5)
  }
} failed to prune expired items

[thisisnkc]

This issue was likely caused by a race condition between the Background Worker (which periodically prunes files) and the Main Thread (performing delete, clear, or prune).

The Flow:

1. The Background Worker lists all files to process.
2. The Main Thread deletes a file immediately after the list is generated but before the Worker processes it.
3. The Worker attempts to readFile() the now-deleted file, throwing an ENOENT error, which is logged.

Possible fix would be - "the Worker just shrugs and says "Okay, file's gone, less work for me" instead of complaining about it.