- 
          
- 
                Notifications
    You must be signed in to change notification settings 
- Fork 4.6k
          fix(32bit): use PHP_INT_MAX where needed
          #52402
        
          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
Conversation
| https://github.com/nextcloud/server/actions/runs/14702311414 Running the 32bit CI on this branch | 
|  | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tests are failing
* Typo from #52392 `0xFFFF` is only 2 bytes, but we need either `0xFFFFFFFF` or maybe a bit easier to read `PHP_INT_MAX`. Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
| @come-nc sorry I thought PHP int max is unsigned 😅 | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤷
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎉
packcompatible with 32bit PHP #523920xFFFFis only 2 bytes, but we need either0xFFFFFFFFor maybe a bit easier to readPHP_INT_MAX.