You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Which package is this bug report for? If unsure which one to select, leave blank
@crawlee/memory-storage
Issue description
I am running an actor locally via apify run then I interrupt it with SIGINT and then I try to run it again.
It happens quite a lot, that i cannot run it again due to error:
SyntaxError: Unexpected end of JSON input
at JSON.parse (<anonymous>)
at findRequestQueueByPossibleId (/home/JJetmar/node_modules/@crawlee/memory-storage/cache-helpers.js:237:42)
at async RequestQueueClient.get (/home/JJetmar/node_modules/@crawlee/memory-storage/resource-clients/request-queue.js:89:23)
at async StorageManager._getOrCreateStorage (/home/JJetmar/node_modules/@crawlee/core/storages/storage_manager.js:97:33)
at async StorageManager.openStorage (/home/JJetmar/node_modules/@crawlee/core/storages/storage_manager.js:73:35)
at async file:///home/JJetmar/src/main.js:90:22
Waiting for the debugger to disconnect...
Error: npm exited with code 1
The issue is a in a request_queue item, that is stored on filesystem and the file is empty.
Code sample
No response
Package version
3.0.4
Node.js version
v16.16.0
Operating system
Linux
Apify platform
Tick me if you encountered this issue on the Apify platform
Which package is this bug report for? If unsure which one to select, leave blank
@crawlee/memory-storage
Issue description
I am running an actor locally via apify run then I interrupt it with SIGINT and then I try to run it again.
It happens quite a lot, that i cannot run it again due to error:
The issue is a in a request_queue item, that is stored on filesystem and the file is empty.
Code sample
No response
Package version
3.0.4
Node.js version
v16.16.0
Operating system
Linux
Apify platform
I have tested this on the
next
releaseNo response
Other context
discussed on https://apifier.slack.com/archives/CD0SF6KD4/p1673522872403149
The text was updated successfully, but these errors were encountered: