-
Notifications
You must be signed in to change notification settings - Fork 36
Description
Apify CLI version:
apify-cli/1.1.1 (6d2b9fa) running on darwin-arm64 with bun-1.2.20 (emulating node 24.3.0), installed via bundle
I initialized a Python project using apify init, wrote some code using standard CLI template for httpx project, edited INPUT.json at ./storage/key_value_stores/default folder and now I'm trying to run the actor locally for testing and every time I'm getting the same log:
[apify] INFO Initializing Actor ({"apify_sdk_version": "3.0.4", "apify_client_version": "2.3.0", "crawlee_version": "1.0.4", "python_version": "3.13.7", "os": "darwin"})
[apify] INFO [Status message]: No requests were processed
[apify] INFO Exiting Actor ({"exit_code": 0})
Error: ENOENT: no such file or directory, stat '/Users/***/dev/products/apify/storage/key_value_stores/default/INPUT.json'
I checked apify run --help but found no option to disable automatic purging.
I even tried writing a bash script that places INPUT.json to its proper place before running the actor:
cp sample_input.json ./storage/key_value_stores/default/INPUT.json
apify run
but keep getting same notorious error every time even though I tried manually placing INPUT.json to ./storage/key_value_stores/default/INPUT.json before executing apify run command:
Error: ENOENT: no such file or directory, stat '/Users/***/dev/products/apify/storage/key_value_stores/default/INPUT.json'
--input-file= doesnt work either, Apify CLI seems to be ignoring that option completely.
I havent had this problem with previous versions of Apify and this issue blocks my ability to test my actor in the local environment.
Can anyone explain if there's something I'm missing and there's a new way to run local test of an actor?