test(gateway): unit regressions for _split_text_chunks under a custom length unit - #55843
Conversation
|
Issue with reproduction: #55844 |
Competing fix cluster for the |
|
Thanks for isolating the fallback chunking defect; the diagnosis is correct on current main. Problems
Suggested changes
Automated hermes-sweeper review. |
3083e76 to
a1b23aa
Compare
Re-triage correction: the current head is a test-only follow-up after the fallback implementation landed elsewhere. It retains direct UTF-16 chunking coverage; the remaining progressive existing-message overflow concern is a separate code-path gap noted in review. Related to #42523 and #55844, not a competing implementation duplicate. |
a1b23aa to
49c0116
Compare
0782064 to
1126e24
Compare
1126e24 to
c0071b7
Compare
… custom length unit The code fix (fallback split honoring the platform length unit, and the progressive existing-message overflow path) has landed on main via the competing fix; the suite still has no direct unit tests of _split_text_chunks with a non-codepoint len_fn. Add the emoji/UTF-16 regression cases: no-newline fallback, newline-in-first-half, and default-len behaviour unchanged.
c0071b7 to
8608203
Compare
Rebased and rescoped: the code fix landed on main via the competing fix in this cluster (the fallback split now uses the codepoint budget, and the progressive existing-message overflow path was corrected as well — both verified on current main).
What remains from this PR is direct unit coverage: the suite exercises the UTF-16 paths at integration level but has no direct unit tests of
_split_text_chunkswith a non-codepointlen_fn. This adds the three regression cases (emoji no-newline fallback, newline-in-first-half, default-lenbehaviour unchanged) from the original report (#55844).