Skip to content

Fix storage calculation bugs causing false insufficient storage alerts#304

Closed
ofirgalcon wants to merge 2 commits intoMacjutsu:5.1.0-beta5from
ofirgalcon:5.1.0-beta5
Closed

Fix storage calculation bugs causing false insufficient storage alerts#304
ofirgalcon wants to merge 2 commits intoMacjutsu:5.1.0-beta5from
ofirgalcon:5.1.0-beta5

Conversation

@ofirgalcon
Copy link

  • Fix NSURLVolumeAvailableCapacityForImportantUsageKey returning 0 GB
  • Fix MSU update size calculation using wrong divisor (/1000000 vs /1000000000)
  • Add fallback mechanism for storage detection
  • Update checksum for integrity verification
  • Add comprehensive documentation

Resolves issues with false 'insufficient storage' alerts and impossible storage requirements (TB bug).

- Fix NSURLVolumeAvailableCapacityForImportantUsageKey returning 0 GB
- Fix MSU update size calculation using wrong divisor (/1000000 vs /1000000000)
- Add fallback mechanism for storage detection
- Update checksum for integrity verification
- Add comprehensive documentation

Resolves issues with false 'insufficient storage' alerts and impossible storage requirements (85TB bug).
Add cache server discovery via AssetCacheLocatorUtil and apply --caching-server to all mist calls, with clean fallback when no cache is found. Ensures installer listing and download workflows leverage local caching without requiring Python.
@Macjutsu
Copy link
Owner

First, thank you for these additional free space methods and spectacular documentation!

However, I chose to manually implement the chagnes. Primarily because I was unable to replicate the MSU update calculatation issues in the original code, and the new code was providing inaccurate results. Perhaps the softwreupdate results you were seeing are different than mine?

https://github.com/Macjutsu/super/releases/tag/v5.1.0-rc4

@Macjutsu Macjutsu closed this Feb 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants