[Miniflare 3] Bump workerd to 1.20230512.0
#575
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cloudflare/workerd#563 added support to R2 bindings for these
|
mrbbot
force-pushed
the
tre-workerd-2023-05-11
branch
from
dbd738f to
0460c89
Compare
Wait for control messages using the new `--control-fd` flag for signalling when `workerd` is ready to receive requests, and the port it's listening on. This allows us to pass port `0` directly to workerd, and have it allocate a free port, preventing races. It also allows us to remove the repeated readiness probes. 🎉
mrbbot
changed the title
workerd to 1.20230511.0workerd to 1.20230512.0
mrbbot
force-pushed
the
tre-workerd-2023-05-11
branch
from
0460c89 to
34f810a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR bumps
workerdto version1.20230511.0, adding support for multiple/weak/wildcard R2 ETags, and getting listening ports from the new--control-fdflag. The R2 ETag stuff should really be in a separate PR, but this version changes the schema for R2 loopback requests, breaking our existing gateway. See cloudflare/workerd#563. The other change here is waiting for control messages using the new--control-fdflag. This signals whenworkerdis ready to receive requests, and the port it's listening on. This allows us to pass port0directly toworkerd, and have it allocate a free port, preventing races. The default port has been changed to0, since that makes more sense for an API. It also allows us to remove the repeated readiness probes. 🎉