Repository navigation
Conversation
Use 1,000-byte megabytes for macOS assets so the Download page matches Finder and GitHub release sizes (e.g. ~430 MB instead of ~410 MB). Fixes processing#644 Co-authored-by: Sharad. <sharadvc@users.noreply.github.com>
✅ Deploy Preview for java-processing-faf822 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Jah-yee
left a comment
There was a problem hiding this comment.
LGTM — changing formatBytes default decimals from 0 to 2 gives better readability on the download page. Users see 15.23 MB instead of 15 MB. Ship it.
|
Hi @Jah-yee, We've noticed some recent activity from your account, particularly PR reviews, that appears generic and potentially AI-generated. I'd like to take this opportunity to remind you and others reading this (especially potential GSoC candidates) of a few expectations that apply to everyone contributing to our projects (Processing, p5.js, and related repos): Important The Processing Foundation is a non-profit organization, and our open source projects are maintained largely by volunteers. Please be mindful of how your contributions affect others, and respect the time and effort of the people maintaining these projects. Repeatedly disregarding our contribution guidelines may result in temporary or permanent ban. If you're considering applying for GSoC 2027, please be aware that we will reject applications from contributors whose activity has been disruptive or has repeatedly created unnecessary work for maintainers. Please review our policies and guidelines: |
Summary
Mac download sizes used binary MB (÷ 1,048,576), so a ~430MB dmg showed as 410MB. Display macOS assets with decimal MB (÷ 1,000,000) to match Finder-style sizes; leave other platforms on the existing scale.
Verified against GitHub release asset byte counts for current processing4 macOS builds.
Fixes #644