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

Can't load dataset items in total size > 512MB #247

Open
valekjo opened this issue May 20, 2022 · 3 comments
Open

Can't load dataset items in total size > 512MB #247

valekjo opened this issue May 20, 2022 · 3 comments
Labels
backend Issues related to the platform backend. bug Something isn't working. low priority Low priority issues to be done eventually. t-platform Issues with this label are in the ownership of the platform team.

Comments

@valekjo
Copy link
Member

valekjo commented May 20, 2022

Node has 512MB limit on string size, if the response from API is larger, the client fails to parse it.

I guess the issue might also manifest in key-value-stores? Other api endpoints probably never produce this large responses.

Reported on slack: https://apifier.slack.com/archives/C0L33UM7Z/p1652976377122799

@valekjo valekjo added the bug Something isn't working. label May 20, 2022
@mnmkng
Copy link
Member

mnmkng commented May 20, 2022

I don't think this is a bug really. It's quite obvious that strings of unlimited sizes cannot be loaded or parsed. That's why the list functions of client have offsets and limits and the KVS functions have stream options.

I would vote for closing this.

@fnesveda
Copy link
Member

@valekjo Where did this bug manifest? Could you link the Slack thread or another discussion where this was reported?

@fnesveda
Copy link
Member

It would also be cool if we supported some client.paginate() function, which automatically iterates over the pages in a list returned by the API, like Octokit does it, but that's not really related to this issue specifically.

@fnesveda fnesveda added next sprint Check this out when planning next sprint. low priority Low priority issues to be done eventually. labels Jun 8, 2022
@gippy gippy added the t-platform Issues with this label are in the ownership of the platform team. label Jun 20, 2022
@fnesveda fnesveda removed the next sprint Check this out when planning next sprint. label Jul 18, 2022
@fnesveda fnesveda added the backend Issues related to the platform backend. label Nov 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend Issues related to the platform backend. bug Something isn't working. low priority Low priority issues to be done eventually. t-platform Issues with this label are in the ownership of the platform team.
Projects
None yet
Development

No branches or pull requests

4 participants