Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[stable25] fix(trashbin): Truncate long filenames #38576

Merged
merged 1 commit into from
Jun 5, 2023

Conversation

backportbot-nextcloud[bot]
Copy link

backport of #38355

Signed-off-by: Christopher Ng <chrng8@gmail.com>
$trashFilename = substr_replace(
$trashFilename,
'',
$maxLength / 2,

Check failure

Code scanning / Psalm

InvalidScalarArgument

Argument 3 of substr_replace expects array<array-key, int>|int, float|int provided
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Psalm error seems legit, this should be an int. How come it did not complain on original PR?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In this case maxLength is always 250 so the result is always int and can be ignored

But the alert likely didn't show initially because it exceeded the limit, see https://github.com/nextcloud/server/security/code-scanning/tools/Psalm/status/configurations/actions-FZTWS5DIOVRC653POJVWM3DPO5ZS643UMF2GSYZNMNXWIZJNMFXGC3DZONUXGLTZNVWA/ce2b36315853290650a327094ccdb926d691e375530fc54471e6d340970bbb9c

@blizzz blizzz merged commit b991751 into stable25 Jun 5, 2023
@blizzz blizzz deleted the backport/38355/stable25 branch June 5, 2023 15:41
@blizzz blizzz mentioned this pull request Jun 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants