-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Remove payload length cap from Event Stream messages #3371
Conversation
Windows builds seem to be struggling with the larger payload. I'll investigate what's currently failing, it's not clear in the logs. |
Codecov ReportAttention: Patch coverage is
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## develop #3371 +/- ##
==========================================
Coverage ? 93.05%
==========================================
Files ? 66
Lines ? 14478
Branches ? 0
==========================================
Hits ? 13472
Misses ? 1006
Partials ? 0 ☔ View full report in Codecov by Sentry. |
26a9b47
to
0fdd458
Compare
0fdd458
to
e079501
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* release-1.36.15: Bumping version to 1.36.15 Update partitions file Update endpoints model Update to latest models Remove payload length cap from Eventstream messages (#3371)
In initial implementations of Event Streams, there was a 16MB payload limit for Event Stream payloads. Anything exceeding that was considered malformed. In more modern implementations, that limit has been raised with some services using 24MB. We'll be removing this client-side check going forward as it doesn't serve a practical purpose. The checksum will be used to validate the payload and size limitations will be left to the service to determine going forward.