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

Error handling for Objects that fail because they're too big #636

Closed
snarfed opened this issue Sep 8, 2023 · 2 comments
Closed

Error handling for Objects that fail because they're too big #636

snarfed opened this issue Sep 8, 2023 · 2 comments
Labels

Comments

@snarfed
Copy link
Owner

snarfed commented Sep 8, 2023

Started seeing this error yesterday on https://maurice-renck.de/de/blog/2023/podcaster-plugin-3 (parsed mf2), which includes a big inlined data: img. Datastore raised google.api_core.exceptions.InvalidArgument: 400 entity is too big, which we don't yet handle, so we 500ed.

Datastore max property value size and entity size are both 1MB. OK. Total parsed mf2 size is only 200KB though, and the converted as1 computed property is similarly ~200KB. So why does the datastore think we're over 1MB?

...arguably it doesn't matter, we should just handle this exception and return HTTP 400.

@snarfed snarfed changed the title Web (etc): don't try to store Object if mf2 is too big Error handling for Objects that fail because they're too big Sep 8, 2023
@snarfed snarfed added now infra and removed now labels May 19, 2024
@snarfed
Copy link
Owner Author

snarfed commented Nov 18, 2024

#1501 is probably the most common cause of this, doing that should help here.

@snarfed
Copy link
Owner Author

snarfed commented Jan 4, 2025

Did #1501, haven't seen this in the last 30d. Tentatively closing.

@snarfed snarfed closed this as completed Jan 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant