-
Notifications
You must be signed in to change notification settings - Fork 73
fix: deployed worker unable to invoke itself in memory queue #445
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
Conversation
🦋 Changeset detectedLatest commit: b7f7b12 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
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 |
commit: |
That's really weird, in the issue they say that it works fine with |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the fix @james-elicx, LGTM.
Maybe add a little more details to the changeset for the changelog
34034e5
to
b7f7b12
Compare
Any chance that direct goes through the path @dario-piotrowicz modified (removing an internal header). |
Just tried the |
Service bindings are required for fetching the same worker in production.
A bit of a shame that our local e2es were unable to catch this as wrangler doesn't fail when doing fetches in local mode.
Docs PR - opennextjs/docs#89