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

FastAPI Example: TypeError: response.body.arrayBuffer is not a function #6

Open
TheBitmonkey opened this issue May 20, 2024 · 6 comments

Comments

@TheBitmonkey
Copy link

I am getting this error on the fastapi example:

Starting local server...
[wrangler:inf] Ready on http://127.0.0.1:8787
Loading fastapi, starlette, anyio, sniffio, openssl, pydantic, typing-extensions, pydantic-core, annotated-types
X [ERROR] Error in makeHandler

X [ERROR] Uncaught (in promise) TypeError: response.body.arrayBuffer is not a function

  at loadBundle (pyodide-internal:loadPackage:36:36)

I can't figure it out at all. Maybe import asgi does not work anymore?

@jcrreis
Copy link

jcrreis commented May 24, 2024

have the same error

@koast18
Copy link

koast18 commented May 26, 2024

same error, it seems something changes breaks that. simply downgrade is a workaround.

npm install [email protected]

@hoodmane
Copy link

Thanks for the report @TheBitmonkey! I'll look into this as soon as I have a moment.

@laike9m
Copy link

laike9m commented Jun 10, 2024

Any update?

@garrettgu10
Copy link
Collaborator

@laike9m a fix is out, i'm going to try to update wrangler tomorrow. Thanks for your patience!

@mikenomitch
Copy link
Contributor

Hey all, a fix for this specific issue is technically out, but FastAPI is still failing due to another issue.

We're currently working on the broader issue, but probably won't have a new version of wrangler out with the fix until next week. Sorry about this :( We are also updating the gaps in automated testing that allowed us to miss this in the first place.

For the time being, if you downgrade to wrangler 3.55.0, you can get FastAPI working. Hopefully this workaround is only needed until next week.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants