RequestQueue2 debug log a lot "Failed to delete request lock for request"

[slow-groovin]

Which package is this bug report for? If unsure which one to select, leave blank

@crawlee/cheerio (CheerioCrawler)

Issue description

After update to 3.10 , the job finished as before, but a lot of Failed to delete request lock for request logs appear

log sample:

WARN  CheerioCrawler: Reclaiming failed request back to the list or queue. Client network socket disconnected before secure TLS connection was established
 {"id":"jSqKj16FjdIxXv7","url":"https://xxxxxx","retryCount":1}
DEBUG RequestQueue2: Failed to delete request lock for request jSqKj16FjdIxXv7 {"err":{"name":"Error","message":"Request with ID jSqKj16FjdIxXv7 is not locked in queue default","stack":"Error: Request with ID jSqKj16FjdIxXv7 is not locked in queue default\n    at RequestQueueClient.deleteRequestLock (/app/node_modules/@crawlee/memory-storage/resource-clients/request-queue.js:257:19)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async RequestQueue.reclaimRequest (/app/node_modules/@crawlee/core/storages/request_queue_v2.js:156:17)\n    at async CheerioCrawler._requestFunctionErrorHandler (/app/node_modules/@crawlee/basic/internals/basic-crawler.js:976:17)\n    at async wrap (/app/node_modules/@apify/timeout/cjs/index.cjs:54:21)"}}

Code sample

No response

Package version

3.10.3

Node.js version

v20.10.0

Operating system

Ubuntu 23

Apify platform

• Tick me if you encountered this issue on the Apify platform

I have tested this on the next release

No response

Other context

No response

[B4nan]

Hi there and sorry for the long wait. The log message is not to be afraid of, in the end, it's logged only to the debug level. We will remove it completely so it's not confusing others. We try to remove locks on some places to be sure the request is not locked, and this only means there was no lock at all.