Skip to content

Fix not starting inspector proxy for miniflare workers created by setOptions #9784

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 2 commits into from
Jul 6, 2025

Conversation

Mkassabov
Copy link
Contributor

@Mkassabov Mkassabov commented Jun 27, 2025

Fixes miniflare workers created by setOptions not being able to be accessed via the inspector proxy

When InspectorProxyController.updateConnection() is called pass in an updated set of workers to inspect. To facilitate creating this set #workerNamesToProxy() has been created on Miniflare since it needs occur multiple times, not just during instantiation.


  • Tests
    • Tests included
    • Tests not necessary because:
  • Public documentation
    • Cloudflare docs PR(s):
    • Documentation not necessary because: miniflare bug fix
  • Wrangler V3 Backport
    • Wrangler PR:
    • Not necessary because: miniflare internal change

@Mkassabov Mkassabov requested a review from a team as a code owner June 27, 2025 22:08
Copy link

changeset-bot bot commented Jun 27, 2025

🦋 Changeset detected

Latest commit: fec8da7

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 5 packages
Name Type
miniflare Patch
@cloudflare/pages-shared Patch
@cloudflare/vite-plugin Patch
@cloudflare/vitest-pool-workers Patch
wrangler Patch

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

Copy link

pkg-pr-new bot commented Jul 1, 2025

create-cloudflare

npm i https://pkg.pr.new/create-cloudflare@9784

@cloudflare/kv-asset-handler

npm i https://pkg.pr.new/@cloudflare/kv-asset-handler@9784

miniflare

npm i https://pkg.pr.new/miniflare@9784

@cloudflare/pages-shared

npm i https://pkg.pr.new/@cloudflare/pages-shared@9784

@cloudflare/unenv-preset

npm i https://pkg.pr.new/@cloudflare/unenv-preset@9784

@cloudflare/vite-plugin

npm i https://pkg.pr.new/@cloudflare/vite-plugin@9784

@cloudflare/vitest-pool-workers

npm i https://pkg.pr.new/@cloudflare/vitest-pool-workers@9784

@cloudflare/workers-editor-shared

npm i https://pkg.pr.new/@cloudflare/workers-editor-shared@9784

wrangler

npm i https://pkg.pr.new/wrangler@9784

commit: fec8da7

@Mkassabov
Copy link
Contributor Author

Seeing tests failing here, but not really sure what to do about them since they seem like credential issues. Is this just a matter of the PR not being from a cloudflare employee?

FWIW this is a purely miniflare change so it shouldn't effect C3.

Please let me know if there is anything I can do to help get this across the line! <3

@petebacondarwin
Copy link
Contributor

Seeing tests failing here, but not really sure what to do about them since they seem like credential issues. Is this just a matter of the PR not being from a cloudflare employee?

FWIW this is a purely miniflare change so it shouldn't effect C3.

Please let me know if there is anything I can do to help get this across the line! <3

Yeah the failing tests are because the PR is on a fork. It is not your fault.
I'll fix and merge. Thanks!

@github-project-automation github-project-automation bot moved this from Untriaged to Approved in workers-sdk Jul 2, 2025
@petebacondarwin petebacondarwin requested a review from a team as a code owner July 2, 2025 08:33
@petebacondarwin petebacondarwin added this pull request to the merge queue Jul 2, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jul 2, 2025
@petebacondarwin petebacondarwin added this pull request to the merge queue Jul 2, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jul 2, 2025
@petebacondarwin petebacondarwin enabled auto-merge July 2, 2025 10:03
@petebacondarwin petebacondarwin added this pull request to the merge queue Jul 2, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jul 2, 2025
@petebacondarwin petebacondarwin added this pull request to the merge queue Jul 2, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jul 2, 2025
@petebacondarwin petebacondarwin added this pull request to the merge queue Jul 2, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jul 2, 2025
@petebacondarwin petebacondarwin added this pull request to the merge queue Jul 2, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jul 2, 2025
@petebacondarwin petebacondarwin added this pull request to the merge queue Jul 2, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jul 2, 2025
@petebacondarwin petebacondarwin added this pull request to the merge queue Jul 2, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jul 2, 2025
@petebacondarwin petebacondarwin added this pull request to the merge queue Jul 2, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jul 2, 2025
@Mkassabov
Copy link
Contributor Author

If this is still having issues because it's a fork I don't mind if somebody from CF just rewrites the changes so they are not in a fork.

More interested in seeing this issue fixed than getting credit for it or anything.

Sorry if I made a mess with this <3

@petebacondarwin
Copy link
Contributor

Don't worry - we are just having some issues with a flakey merge queue. Will land it today.

@petebacondarwin petebacondarwin added this pull request to the merge queue Jul 6, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jul 6, 2025
@petebacondarwin petebacondarwin added this pull request to the merge queue Jul 6, 2025
Merged via the queue into cloudflare:main with commit 1a75f85 Jul 6, 2025
32 of 33 checks passed
@github-project-automation github-project-automation bot moved this from Approved to Done in workers-sdk Jul 6, 2025
@workers-devprod workers-devprod added the contribution [Holopin] Recognizes an open-source contribution, big or small label Jul 6, 2025
Copy link

holopin-bot bot commented Jul 6, 2025

Congratulations @Mkassabov, the maintainer of this repository has issued you a holobyte! Here it is: https://holopin.io/holobyte/cmcs26y5t659907jucmpwuije

This badge can only be claimed by you, so make sure that your GitHub account is linked to your Holopin account. You can manage those preferences here: https://holopin.io/account.
Or if you're new to Holopin, you can simply sign up with GitHub, which will do the trick!

@workers-devprod workers-devprod mentioned this pull request Jul 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
contribution [Holopin] Recognizes an open-source contribution, big or small
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

3 participants