You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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 raisedgoogle.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.
The text was updated successfully, but these errors were encountered: