-
Notifications
You must be signed in to change notification settings - Fork 779
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
startDevWorker Milestone 1 - Reboot #4175
Conversation
|
A wrangler prerelease is available for testing. You can install this latest build in your project with: npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/6720209255/npm-package-wrangler-4175 You can reference the automatically updated head of this PR with: npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/prs/6720209255/npm-package-wrangler-4175 Or you can use npx https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/6720209255/npm-package-wrangler-4175 dev path/to/script.js Additional artifacts:npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/6720209255/npm-package-cloudflare-pages-shared-4175 Note that these links will no longer work once the GitHub Actions artifact expires.
| Please ensure constraints are pinned, and |
Codecov Report
@@ Coverage Diff @@
## main #4175 +/- ##
==========================================
+ Coverage 75.38% 75.65% +0.26%
==========================================
Files 223 237 +14
Lines 12327 12507 +180
Branches 3187 3198 +11
==========================================
+ Hits 9293 9462 +169
- Misses 3034 3045 +11
|
@RamIdeas would it be possible to separate out the individual bug fixes into separate PRs? |
bed083f
to
cdfb63c
Compare
@penalosa the 2 commits to fix 2 of the bugs were quite tiny and encapsulated in individual commits. I think reviewing each commit will be easy enough If there are bigger changes, I will absolutely open a separate PR 👍 |
cdfb63c
to
83af6d8
Compare
I tested this in my project and seeing warning released to When testing locally on Windows 10 I also get the following additional messages to stderr
|
Does this help with supporting |
7ee52ca
to
f698350
Compare
This reverts commit 88f15f6.
unless log level is debug change ProxyControllerLogger info override to log override change WranglerLog info override to log override -- this worksaround an internal Miniflare change
remote inspector websocket upgrade request required auth headers so use `fetch` with `Upgrade: websocket` header instead of `new WebSocket`
instead of UserWorker
This reverts commit 1e6879b. This commit will be reapplied in the Milestone 2 PR.
for (Inspector)ProxyWorker
upon UserWorker restarts
previously, sequential cleanups fail to fully cleanup if earlier steps in the sequence fail
c1b209c
to
2bf4d46
Compare
remove assertion proxyWorker miniflare instance is different
55fc364
to
7cf9069
Compare
436a320
to
9cc5516
Compare
across all packages/fixtures
to force different port across reloads to workaround workerd bug on Windows
eae8bec
to
6b99cab
Compare
Hi @Cyb3r-Jak3! Thanks for your feedback and apologies for the delay. We used your test suite to analyse the stability of these changes. Github got a bit confused with this PR and so I closed this and opened a new PR #4413 – could you try the prerelease build from there and let us know how it goes please? |
@jadbox although we are not focusing on pages dev directly, |
This is the PR to reintroduce #3960
TODO:
🐛 BUG: EBUSY: resource busy or locked, rmdir #4167🐛 BUG: dyld: Symbol not found: _MTLCommonCounterClipperInvocations #4166wrangler dev --remote
no longer logs? #4165What this PR solves / how to test:
Please use the prerelease builds in the bot comment below to test:
wrangler dev
,wrangler dev --remote
,unstable_dev()
in local and remote mode, on your setup and post your issues in comments belowAssociated docs issue(s)/PR(s):
Author has included the following, where applicable:
Reviewer is to perform the following, as applicable:
Note for PR author:
We want to celebrate and highlight awesome PR review! If you think this PR received a particularly high-caliber review, please assign it the label
highlight pr review
so future reviewers can take inspiration and learn from it.