-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Request timeout with a Cloud Function that returns large JSON payload #261
Comments
This will encode all ParseObject on the correct way so they can be translated into PFObject by the IOS SDK.
Yes, I know... I'm looking for other to correct the ParseObject JSON Take a look of this bug: #112 |
@bourquep Was this something which worked on hosted Parse or something new?. Maybe we could add a raw response method (if the response isn't parse objects)? |
Yes, it was working fine on hosted Parse. I have a lot of Cloud Functions that return "custom" JSON (array of non-Parse objects), and it's always been running smoothly on hosted Parse. I could live with a raw response method if there is no other way. |
But if |
Can you measure the time of Parse._encode with your payload? |
Sure! I might only have time to do it next week though. |
@gfosco can you please take a look of this parse-community/Parse-SDK-JS#199 ? I still think the promblem is on the parse-SDK-JS... |
Any chance we can get a payload example to process, @bourquep ? |
Going to close this.. If you can reproduce and provide more details with 2.1.3+ please create a new issue. Thanks. |
I have a Cloud Function that returns a large JSON payload (~1 meg), and which worked fine until updating to v2.0.7, but now leads to a HTTP request timeout (30s) error.
Reverting commit 36675a9 makes it work again.
Looks like
Parse._encode
is doing some heavy processing on the JSON payload and is hanging my request.The text was updated successfully, but these errors were encountered: