-
Notifications
You must be signed in to change notification settings - Fork 1.1k
fix(wrangler): Local schedule worker warning message is missing a port #11731
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
🦋 Changeset detectedLatest commit: f80a3e8 The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
create-cloudflare
@cloudflare/kv-asset-handler
miniflare
@cloudflare/pages-shared
@cloudflare/unenv-preset
@cloudflare/vite-plugin
@cloudflare/vitest-pool-workers
@cloudflare/workers-editor-shared
@cloudflare/workers-utils
wrangler
commit: |
| logger.once.warn( | ||
| `Scheduled Workers are not automatically triggered during local development.\n` + | ||
| `To manually trigger a scheduled event, run:\n` + | ||
| ` curl "http://${host}:${userWorkerUrl.port}/cdn-cgi/handler/scheduled"\n` + |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note
This does fix it so there is now a correct and working address provided, but only by providing the Miniflare port. This means the URL logged will differ from the final Ready at http://localhost:8787 URL shown below this warning message.
To manually trigger a scheduled event, run:
curl "http://127.0.0.1:61307/cdn-cgi/handler/scheduled"
|
Claude finished @NuroDev's task —— View job Changeset Review✅ All changesets look good
The changeset
|
|
Closing in favour of #11494 |
Right now if you add a schedule trigger / cron to an existing working and forget to enable the
--test-scheduledit shows the following warning:The warning is correct, bug as you can see the port for the
curlcommand is marked asundefined. This PR fixes that so the port is correctly assigned to the port of the dev server.A picture of a cute animal (not mandatory, but encouraged)