Skip to content
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

Fix edge workers being re-used unexpectedly #41402

Merged
merged 7 commits into from Oct 14, 2022

Conversation

ijjk
Copy link
Member

@ijjk ijjk commented Oct 14, 2022

This ensures we don't re-use edge workers locally as they are meant to be isolated.

Bug

  • Related issues linked using fixes #number
  • Integration tests added
  • Errors have a helpful link attached, see contributing.md

Fixes: slack thread

huozhi
huozhi previously approved these changes Oct 14, 2022
@ijjk ijjk marked this pull request as draft October 14, 2022 04:56
@ijjk ijjk marked this pull request as ready for review October 14, 2022 05:53
@ijjk ijjk merged commit 889af9f into vercel:canary Oct 14, 2022
@ijjk ijjk deleted the fix/isolate-edge-workers branch October 14, 2022 05:56
Kikobeats pushed a commit to Kikobeats/next.js that referenced this pull request Oct 24, 2022
This ensures we don't re-use edge workers locally as they are meant to
be isolated.

## Bug

- [x] Related issues linked using `fixes #number`
- [x] Integration tests added
- [ ] Errors have a helpful link attached, see `contributing.md`

Fixes: [slack
thread](https://vercel.slack.com/archives/C035J346QQL/p1665708744315109)
ijjk added a commit that referenced this pull request Nov 6, 2022
Follow-up to #41402 this
re-enables the sandbox cache and updates to leverage our global
`AsyncLocalStorage` for isolating request meta in both the edge and
Node.js runtime.

Closes: #42349
Closes: #38235
Closes: #42225
Closes: #42351

## Bug

- [x] Related issues linked using `fixes #number`
- [ ] Integration tests added
- [ ] Errors have a helpful link attached, see `contributing.md`

## Feature

- [ ] Implements an existing feature request or RFC. Make sure the
feature request has been accepted for implementation before opening a
PR.
- [ ] Related issues linked using `fixes #number`
- [ ] Integration tests added
- [ ] Documentation added
- [ ] Telemetry added. In case of a feature if it's used or not.
- [ ] Errors have a helpful link attached, see `contributing.md`

## Documentation / Examples

- [ ] Make sure the linting passes by running `pnpm build && pnpm lint`
- [ ] The "examples guidelines" are followed from [our contributing
doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 16, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants