Skip to content

[Queues] Update local development known issues #21977

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

Merged
merged 8 commits into from
Apr 25, 2025
Merged

Conversation

harshil1712
Copy link
Contributor

Summary

Update the known issues for local dev, and added instructions on how to run separate producer and consumer Workers. Addresses #21208

Documentation checklist

@harshil1712 harshil1712 requested review from elithrar, maheshwarip and a team as code owners April 25, 2025 14:17
@github-actions github-actions bot added size/s product:queues Cloudflare Queues: https://developers.cloudflare.com/queues labels Apr 25, 2025
Copy link
Contributor

hyperlint-ai bot commented Apr 25, 2025

Howdy and thanks for contributing to our repo. The Cloudflare team reviews new, external PRs within two (2) weeks. If it's been two weeks or longer without any movement, please tag the PR Assignees in a comment.

We review internal PRs within 1 week. If it's something urgent or has been sitting without a comment, start a thread in the Developer Docs space internally.


PR Change Summary

Updated the known issues for local development and provided instructions for running separate producer and consumer Workers.

  • Added instructions for running separate producer and consumer Workers locally using an experimental feature.
  • Updated the known issues section to reflect current limitations with local development.
  • Clarified that remote queue connections are not supported during local development.

Modified Files

  • src/content/docs/queues/configuration/local-development.mdx

How can I customize these reviews?

Check out the Hyperlint AI Reviewer docs for more information on how to customize the review.

If you just want to ignore it on this PR, you can add the hyperlint-ignore label to the PR. Future changes won't trigger a Hyperlint review.

Note specifically for link checks, we only check the first 30 links in a file and we cache the results for several hours (for instance, if you just added a page, you might experience this). Our recommendation is to add hyperlint-ignore to the PR to ignore the link check for this PR.

Copy link
Contributor

@maheshwarip maheshwarip left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @harshil1712, this is a good start! But could we add a bit more information here?

  1. What is the recommended project structure for a user to run separate producer & consumer workers?
  2. Could we add the output from running this command? npx wrangler dev -c ./wrangler.jsonc -c ../consumer-worker/wrangler.jsonc --persist-to .wrangler/state ?
  3. I'd recommend putting this under a new heading: Separating producer & consumer Workers
  4. Could we mark this as Experimental by adding the same warning that's attached here? https://developers.cloudflare.com/workers/runtime-apis/bindings/service-bindings/#local-development

@harshil1712 harshil1712 requested a review from maheshwarip April 25, 2025 15:09
@maheshwarip maheshwarip merged commit 610468e into production Apr 25, 2025
13 checks passed
@maheshwarip maheshwarip deleted the queues-local-dev branch April 25, 2025 19:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
product:queues Cloudflare Queues: https://developers.cloudflare.com/queues size/s
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants