Skip to content

decodeBuffered APIs should all be configurable to throw the EncodingSizeException #224

Description

@05nelsonm

Having trouble squaring a circle in kmp-file whereby if a consumer writes text to a file which, when ran through decodeBuffered, the UTF-8 byte size exceeds Int.MAX_VALUE, they cannot then read the file because its size is greater than Int.MAX_VALUE.

There needs to be a parameter throwSizeException or something.

kmp-file and kmp-process are already using the 2 parameter decodeBufferedanddecodeBufferedAsyncfunctions from theSNAPSHOTpublication, so those should be duplicated and marked as deprecated until2.6.0` release is cut; a separate issue will be created to ensure that happens.

All functions should require the parameter be specified.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions