🐛 BUG: "scheduled" template broken #4560

Akiyamka · 2023-12-06T19:21:18Z

Which Cloudflare product(s) does this pertain to?

Workers Runtime

What version(s) of the tool(s) are you using?

wrangler 3.19.0

What version of Node are you using?

v20.8.0

What operating system are you using?

Linux

Describe the Bug

Steps:

pnpm create cloudflare@latest
In which directory do you want to create your application? : ./daemon
What type of application do you want to create? type Scheduled Worker (Cron Trigger)
Do you want to use TypeScript?: Yes
(skip deploy step)
cd ./daemon
npx wrangler dev

[wrangler:inf] Ready on http://localhost:8787
at __facade_modules_fetch__ (/home/user/git/_experements/ustatus/daemon/.wrangler/tmp/bundle-JfDMqA/middleware-loader.entry.ts:45:9)
   at __facade_invokeChain__ (/home/user/git/_experements/ustatus/daemon/node_modules/.pnpm/[email protected]/node_modules/wrangler/templates/middleware/common.ts:53:9)
   at Object.next (/home/user/git/_experements/ustatus/daemon/node_modules/.pnpm/[email protected]/node_modules/wrangler/templates/middleware/common.ts:50:11)
   at jsonError (/home/user/git/_experements/ustatus/daemon/node_modules/.pnpm/[email protected]/node_modules/wrangler/templates/middleware/middleware-miniflare3-json-error.ts:22:30)
   at __facade_invokeChain__ (/home/user/git/_experements/ustatus/daemon/node_modules/.pnpm/[email protected]/node_modules/wrangler/templates/middleware/common.ts:53:9)
   at __facade_invoke__ (/home/user/git/_experements/ustatus/daemon/node_modules/.pnpm/[email protected]/node_modules/wrangler/templates/middleware/common.ts:63:9)
   at Object.fetch (/home/user/git/_experements/ustatus/daemon/.wrangler/tmp/bundle-JfDMqA/middleware-loader.entry.ts:114:11)

Please provide a link to a minimal reproduction

No response

Please provide any relevant error logs

pnpm create cloudflare@latest
.../share/pnpm/store/v3/tmp/dlx-11402    | Progress: resolved 1, reused 0, dow
.../share/pnpm/store/v3/tmp/dlx-11402    |   +1 +
.../share/pnpm/store/v3/tmp/dlx-11402    | Progress: resolved 1, reused 0, dow
.../share/pnpm/store/v3/tmp/dlx-11402    | Progress: resolved 1, reused 0, dow
.../share/pnpm/store/v3/tmp/dlx-11402    | Progress: resolved 1, reused 0, dow
nloaded 1, added 1, done

using create-cloudflare version 2.8.1

╭ Create an application with Cloudflare Step 1 of 3
│
├ In which directory do you want to create your application?
│ dir ./daemon
│
├ What type of application do you want to create?
│ type Scheduled Worker (Cron Trigger)
│
├ Do you want to use TypeScript?
│ yes typescript
│
├ Copying files from "scheduled" template
│
├ Retrieving current workerd compatibility date
│ compatibility date 2023-11-21
│
╰ Application created

╭ Installing dependencies Step 2 of 3
│
├ Installing dependencies
│ installed via `pnpm install`
│
├ Installing @cloudflare/workers-types
│ installed via pnpm
│
├ Adding latest types to `tsconfig.json`
│ added @cloudflare/workers-types/2023-07-01
│
╰ Dependencies Installed

╭ Deploy with Cloudflare Step 3 of 3
│
├ Do you want to deploy your application?
│ yes deploy via `pnpm run deploy`
│
├ Logging into Cloudflare checking authentication status
│ not logged in
│
├ Logging into Cloudflare This will open a browser window
│ allowed via `wrangler login`
│
├ Selecting Cloudflare account retrieving accounts
│ account [email protected]'s Account
│
├ Deploying your application
│
> [email protected] deploy /home/user/git/_experements/ustatus/daemon
> wrangler deploy

 ⛅ wrangler 3.19.0
-------------------
Total Upload: 0.45 KiB / gzip: 0.31 KiB
▲ [WARNING] You need to register a workers.dev subdomain before publishing to workers.dev


? Would you like to register a workers.dev subdomain now?
🤖 Using default value in non-interactive context: yes

✘ [ERROR] This command cannot be run in a non-interactive context


If you think this is a bug then please create an issue at https://github.com/cloudflare/workers-sdk/issues/new/choose
🪵  Logs were written to "/home/user/.config/.wrangler/logs/wrangler-2023-12-06_18-46-43_164.log"
 ELIFECYCLE  Command failed with exit code 1.

│
Error:
> [email protected] deploy /home/user/git/_experements/ustatus/daemon
> wrangler deploy

 ⛅ wrangler 3.19.0
-------------------
Total Upload: 0.45 KiB / gzip: 0.31 KiB
▲ [WARNING] You need to register a workers.dev subdomain before publishing to workers.dev


? Would you like to register a workers.dev subdomain now?
🤖 Using default value in non-interactive context: yes

✘ [ERROR] This command cannot be run in a non-interactive context


If you think this is a bug then please create an issue at https://github.com/cloudflare/workers-sdk/issues/new/choose
🪵  Logs were written to "/home/user/.config/.wrangler/logs/wrangler-2023-12-06_18-46-43_164.log"
 ELIFECYCLE  Command failed with exit code 1.

╭─ in ~/git/_experements/ustatus on main✘✘✘
╰─± ls
daemon  devbox.json  devbox.lock  package.json
╭─ in ~/git/_experements/ustatus on main✘✘✘
╰─± cd daemon
╭─ in ~/git/_experements/ustatus/daemon on main✘✘✘
╰─±  npx wrangler dev
 ⛅ wrangler 3.19.0
-------------------
✔ Would you like to help improve Wrangler by sending usage metrics to Cloudflare? … yes
Your choice has been saved in the following file: ../../../../.config/.wrangler/metrics.json.

  You can override the user level setting for a project in `wrangler.toml`:

   - to disable sending metrics for a project: `send_metrics = false`
   - to enable sending metrics for a project: `send_metrics = true`
⎔ Starting local server...
▲ [WARNING] Miniflare 3 does not support CRON triggers yet, ignoring...


[wrangler:inf] Ready on http://localhost:8787
[wrangler:err] Error: Handler does not export a fetch() function.
    at __facade_modules_fetch__ (/home/user/git/_experements/ustatus/daemon/.wrangler/tmp/bundle-JfDMqA/middleware-loader.entry.ts:45:9)
    at __facade_invokeChain__ (/home/user/git/_experements/ustatus/daemon/node_modules/.pnpm/[email protected]/node_modules/wrangler/templates/middleware/common.ts:53:9)
    at Object.next (/home/user/git/_experements/ustatus/daemon/node_modules/.pnpm/[email protected]/node_modules/wrangler/templates/middleware/common.ts:50:11)
    at jsonError (/home/user/git/_experements/ustatus/daemon/node_modules/.pnpm/[email protected]/node_modules/wrangler/templates/middleware/middleware-miniflare3-json-error.ts:22:30)
    at __facade_invokeChain__ (/home/user/git/_experements/ustatus/daemon/node_modules/.pnpm/[email protected]/node_modules/wrangler/templates/middleware/common.ts:53:9)
    at __facade_invoke__ (/home/user/git/_experements/ustatus/daemon/node_modules/.pnpm/[email protected]/node_modules/wrangler/templates/middleware/common.ts:63:9)
    at Object.fetch (/home/user/git/_experements/ustatus/daemon/.wrangler/tmp/bundle-JfDMqA/middleware-loader.entry.ts:114:11)
[wrangler:inf] GET / 500 Internal Server Error (115ms)
[wrangler:err] Error: Handler does not export a fetch() function.
    at __facade_modules_fetch__ (/home/user/git/_experements/ustatus/daemon/.wrangler/tmp/bundle-JfDMqA/middleware-loader.entry.ts:45:9)
    at __facade_invokeChain__ (/home/user/git/_experements/ustatus/daemon/node_modules/.pnpm/[email protected]/node_modules/wrangler/templates/middleware/common.ts:53:9)
    at Object.next (/home/user/git/_experements/ustatus/daemon/node_modules/.pnpm/[email protected]/node_modules/wrangler/templates/middleware/common.ts:50:11)
    at jsonError (/home/user/git/_experements/ustatus/daemon/node_modules/.pnpm/[email protected]/node_modules/wrangler/templates/middleware/middleware-miniflare3-json-error.ts:22:30)
    at __facade_invokeChain__ (/home/user/git/_experements/ustatus/daemon/node_modules/.pnpm/[email protected]/node_modules/wrangler/templates/middleware/common.ts:53:9)
    at __facade_invoke__ (/home/user/git/_experements/ustatus/daemon/node_modules/.pnpm/[email protected]/node_modules/wrangler/templates/middleware/common.ts:63:9)
    at Object.fetch (/home/user/git/_experements/ustatus/daemon/.wrangler/tmp/bundle-JfDMqA/middleware-loader.entry.ts:114:11)
[wrangler:inf] GET /favicon.ico 500 Internal Server Error (17ms)
╭────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ [b] open a browser, [d] open Devtools, [l] turn off local mode, [c] clear console, [x] to exit                                                                                                                                             │
╰────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
⎔ Shutting down local server...

The text was updated successfully, but these errors were encountered:

admah · 2023-12-06T22:55:32Z

@Akiyamka sorry you've had this issue. This appears to be a duplicate of #4263. In the meantime, you can either run wrangler deploy directly from the created folder or deploy it via the dashboard.

I wasn't able to replicate the fetch error that you have from the example code we provide.

I'm going to close this issue for now as a duplicate. Thanks!

Akiyamka · 2023-12-07T08:50:21Z

@admah , I'm afraid you closed this issue by mistake, my problem is not related to the "cannot be run in a non-interactive context" message (even though it is in the logs).
If you look further and pay attention to the steps I mentioned, and look at the error message - you will notice that the problem is with the worker script template.
As I managed to find out, a fetch hook must be present in the worker, which is absent in the example
To put it simply - the template contains non-valid code, it lacks the export of fetch function

admah · 2023-12-21T18:10:50Z

@Akiyamka the template is not wrong here, other than the need for a JSON.stringify around one of the logged items. It is a valid scheduled Worker. The issue is related to some confusing error messaging that you're seeing. The browser has an automatic request for /favicon.ico that is not being handled properly by us in this instance and causing the error.

In the meantime, you can test your scheduled Worker via wrangler dev --test-scheduled and then run the scheduled event by visiting http://localhost:8787/__scheduled?cron=*+*+*+*+*. You should see the logs in your CLI, and the proper response from the URL.

wim-web · 2024-01-02T18:52:47Z

I have same issue

wim-web · 2024-01-02T19:03:22Z

In my environment, did not give me an error via curl, but via browser did

arthureberledev · 2024-03-17T14:41:52Z

i have the same issue on a fresh project initialized with npm create cloudflare@latest and selected cron job worker template (windows 11)

kaaaaaaaaaaai · 2024-03-20T07:35:05Z

same

jwcheon · 2024-05-09T18:03:32Z

same issue :(

Akiyamka added the bug Something that isn't working label Dec 6, 2023

admah closed this as completed Dec 6, 2023

admah added the c3 Relating to C3 (create-cloudflare) package label Dec 6, 2023

admah reopened this Dec 21, 2023

admah mentioned this issue Dec 21, 2023

🐛 BUG: Detect request to /favicon.ico and return 404 for Workers with no fetch handler #4653

Open

admah removed the c3 Relating to C3 (create-cloudflare) package label Dec 21, 2023

connorads mentioned this issue Apr 7, 2024

C3: Improve cron/scheduled template docs #5547

Merged

9 tasks

workers-devprod mentioned this issue May 16, 2024

Version Packages #5837

Merged

petebacondarwin closed this as completed in #5837 May 17, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

🐛 BUG: "scheduled" template broken #4560

🐛 BUG: "scheduled" template broken #4560

Akiyamka commented Dec 6, 2023 •

edited

admah commented Dec 6, 2023 •

edited

Akiyamka commented Dec 7, 2023 •

edited

admah commented Dec 21, 2023 •

edited

wim-web commented Jan 2, 2024

wim-web commented Jan 2, 2024

arthureberledev commented Mar 17, 2024

kaaaaaaaaaaai commented Mar 20, 2024

jwcheon commented May 9, 2024

🐛 BUG: "scheduled" template broken #4560

🐛 BUG: "scheduled" template broken #4560

Comments

Akiyamka commented Dec 6, 2023 • edited

Which Cloudflare product(s) does this pertain to?

What version(s) of the tool(s) are you using?

What version of Node are you using?

What operating system are you using?

Describe the Bug

Please provide a link to a minimal reproduction

Please provide any relevant error logs

admah commented Dec 6, 2023 • edited

Akiyamka commented Dec 7, 2023 • edited

admah commented Dec 21, 2023 • edited

wim-web commented Jan 2, 2024

wim-web commented Jan 2, 2024

arthureberledev commented Mar 17, 2024

kaaaaaaaaaaai commented Mar 20, 2024

jwcheon commented May 9, 2024

Akiyamka commented Dec 6, 2023 •

edited

admah commented Dec 6, 2023 •

edited

Akiyamka commented Dec 7, 2023 •

edited

admah commented Dec 21, 2023 •

edited