Skip to content

fix(finance): enforce the CSV size cap in UTF-8 bytes - #202

Open
BigDataDZ wants to merge 1 commit into
CopilotKit:mainfrom
BigDataDZ:codex/fix-csv-utf8-size-limit
Open

BigDataDZ wants to merge 1 commit into
CopilotKit:mainfrom
BigDataDZ:codex/fix-csv-utf8-size-limit

Conversation

@BigDataDZ

Copy link
Copy Markdown
Contributor

The advertised 500 KB transaction CSV limit currently counts UTF-16 code units. Chinese, emoji and other multibyte content can therefore exceed the file-size limit while being accepted.

Count UTF-8 bytes before parsing while keeping the existing 500,000-byte threshold and error message. Regression coverage verifies an oversized Chinese import is rejected and that ASCII, Chinese and emoji imports at exactly 500,000 bytes retain their transaction text and amount; one additional byte is rejected.

Validation: both new regressions failed against main before the fix; finance tests 9/9; full suite 486 passed, 3 platform-dependent skips, 0 failed. Repository lint, server/mobile/worker typechecks and server build pass. Independent review found no actionable issues. This changes only the server-side CSV input limit.

This branch has not been deployed

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant