Skip to content

Conversation

@backportbot-nextcloud
Copy link

backport of #35015

There is an issue(bug) when using UTF-8 symbols in any method, which checks the length of string as `isset($id[64])`. You can set only 32 UTF-8 symbols because they are 2 byte, and this "array" check seems inapropriate in this case, as it throws unexpected exceptions.

Signed-off-by: natoponen <[email protected]>
@szaimen szaimen requested review from a team, PVince81, come-nc and icewind1991 and removed request for a team November 11, 2022 23:43
@szaimen szaimen added the 3. to review Waiting for reviews label Nov 11, 2022
@come-nc
Copy link
Contributor

come-nc commented Nov 14, 2022

@nickvergessen Won’t that cause trouble in databases or clients?
Is there a hard limit on notification subject string size in memory?

@nickvergessen
Copy link
Member

nickvergessen commented Nov 14, 2022

Won’t that cause trouble in databases or clients?

Yeah that should break if an app really uses 64 utf8 chars on mysql without utf8mb4 support.

Is there a hard limit on notification subject string size in memory?

The subject is free in length (will be trimmed on pushing, but the API can return the full length.

@nickvergessen
Copy link
Member

This breaks on mysql without utf8mb4 support and is an unintended API change.

@nickvergessen nickvergessen deleted the backport/35015/stable25 branch November 14, 2022 10:16
@nickvergessen
Copy link
Member

Also, why did the codeownership not require my reviews:
grafik

Oh... that's why.

Fix in #35142

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

Labels

3. to review Waiting for reviews bug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants