-
Notifications
You must be signed in to change notification settings - Fork 563
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
Anilist info route for some animes is giving errors #565
Comments
@VISHWAJ33T This error is caused by you attempting to request more data than Vercal allows (5 MBs). This issue will occur when loading certain shows, like ONE PIECE, which has a large amount of episodes that can return responses up to 18 MB. |
any fix for this? |
@kurays015 No not really, you can either attempt to give smaller responses (use different provider), avoid shows like ONE PIECE, or you can self host/find another hosting provider. Unless you're willing to pay, I doubt vercal would be willing to remove the limit, sorry. |
@CADIndie do you know any other free hosting provider? i hosted it on render and it is giving response but it is very slow |
@VISHWAJ33T Sadly not, I did look myself for a while but I resorted to self hosting. If you’re up for it and have the knowledge, you can host a free AWS EC2, Google Cloud e2mini, or Google Cloud Serverless Function instance but it’s only temporary as the credits you get for free do expire. |
I had a similar issue but with some other function. The reason for this is that the maximum payload limit on Vercel is 4.5 MB. If you try to go beyond that then your function will crash. There's no way to bypass this limit. |
Yes that is quite literally what I said. |
Describe the bug
Anilist Info route for some of the animes is giving "This Serverless Function has crashed. " error
Steps to reproduce
meta/anilist/info/16498
meta/anilist/info/113415
meta/anilist/info/16498?provider=zoro
meta/anilist/info/113415?provider=zoro
Expected behavior
Should fetch data
Actual behavior
Additional context
No response
The text was updated successfully, but these errors were encountered: