Apify

Apify Discord Mirror

Updated 2 months ago

Lock file already held

At a glance
The community member is encountering an issue with a lock file being held, which is causing an error when trying to return a response. The community member states that they do not need to persist state, as they are returning it in memory. There are no comments provided, so the summary is based solely on the information in the post.
JJack
·
Hi I seem to be running into this issue with lock file being held? I don't need to persist state as I'm returning it in memory

Plain Text
                return callback(Object.assign(new Error('Lock file is already being held'), { code: 'ELOCKED', file }));
                                              ^

Error: Lock file is already being held
    at /Users/jwarder/Workspace/bypigeon-address/node_modules/proper-lockfile/lib/lockfile.js:68:47
    at callback (/Users/jwarder/Workspace/bypigeon-address/node_modules/graceful-fs/polyfills.js:306:20)
    at FSReqCallback.oncomplete (node:fs:202:5)
    at FSReqCallback.callbackTrampoline (node:internal/async_hooks:130:17) {
  code: 'ELOCKED',
  file: '/Users/jwarder/Workspace/bypigeon-address/storage/key_value_stores/default/SDK_SESSION_POOL_STATE.json'
}
`
Add a reply
Sign up and join the conversation on Discord