Lami•7mo ago

Deployctl, error: Uncaught (in promise) NotFound: Failed to spawn 'start': program not found

> deployctl logs a
i Provisioning a new access token...
i Authorization URL: https://dash.deno.com/signin/cli?claim_challenge=example
error: Uncaught (in promise) NotFound: Failed to spawn 'start': program not found
      .spawn()
       ^
    at spawnChildInner (ext:runtime/40_process.js:164:17)
    at spawnChild (ext:runtime/40_process.js:185:10)
    at Command.spawn (ext:runtime/40_process.js:453:12)
    at provision (https://deno.land/x/deploy@1.9.0/src/utils/access_token.ts:63:8)
    at eventLoopTick (ext:core/01_core.js:181:11)
    at async Object.provision (https://deno.land/x/deploy@1.9.0/src/utils/access_token.ts:13:19)
    at async API.#request (https://deno.land/x/deploy@1.9.0/src/utils/api.ts:99:44)
    at async API.#requestJson (https://deno.land/x/deploy@1.9.0/src/utils/api.ts:121:17)
    at async default (https://deno.land/x/deploy@1.9.0/src/subcommands/logs.ts:112:27)
    at async https://deno.land/x/deploy@1.9.0/deployctl.ts:93:5

> deployctl logs a
i Provisioning a new access token...
i Authorization URL: https://dash.deno.com/signin/cli?claim_challenge=example
error: Uncaught (in promise) NotFound: Failed to spawn 'start': program not found
      .spawn()
       ^
    at spawnChildInner (ext:runtime/40_process.js:164:17)
    at spawnChild (ext:runtime/40_process.js:185:10)
    at Command.spawn (ext:runtime/40_process.js:453:12)
    at provision (https://deno.land/x/deploy@1.9.0/src/utils/access_token.ts:63:8)
    at eventLoopTick (ext:core/01_core.js:181:11)
    at async Object.provision (https://deno.land/x/deploy@1.9.0/src/utils/access_token.ts:13:19)
    at async API.#request (https://deno.land/x/deploy@1.9.0/src/utils/api.ts:99:44)
    at async API.#requestJson (https://deno.land/x/deploy@1.9.0/src/utils/api.ts:121:17)
    at async default (https://deno.land/x/deploy@1.9.0/src/subcommands/logs.ts:112:27)
    at async https://deno.land/x/deploy@1.9.0/deployctl.ts:93:5

When I try to check the Deno Deploy logs from Deployctl, an error occurs and I cannot log in.

> deno --version
deno 1.39.1 (release, x86_64-pc-windows-msvc)
v8 12.0.267.8
typescript 5.3.3

> deno --version
deno 1.39.1 (release, x86_64-pc-windows-msvc)
v8 12.0.267.8
typescript 5.3.3

1 Reply

Deno AI Helper•7mo ago

I wasn't able to find the answer to your question in the official Deno documentation. From the error message you've provided, it seems like the deployctl command is trying to spawn a process with the name 'start', which is not found. This could be related to how processes are spawned on your operating system, especially if you're using Windows. The error is occurring in the provision function, which is part of the deployctl tool, as it tries to open an authorization URL in your default web browser. The 'start' command is typically used on Windows to open files or URLs with the default program. If 'start' is not found, it could indicate an issue with your system's PATH environment variable or how the command is being invoked. Please note that this advice is not based on the Deno documentation, and I would advise you to double-check the accuracy of this advice. It might be helpful to ensure that your system's PATH environment variable is correctly configured to include the necessary directories for running system commands. If the issue persists, you may want to seek assistance from the Deno community or check for updates and bug reports related to deployctl.

Helpful Links: Projects and deployments | Deno Docs Using deployctl on the command line | Deno Docs Deno 1.29: Custom npm registry support API Reference | Deno Docs