discourse/app
Blake Erickson b73a133bb5 FIX: Prevent scientific notation in free space check (#8473)
It's possibly that when trying to upload a backup the free space check
will output scientific notation resulting in an incorrect "There is not
enough space on disk" error.

The free space check uses the Linux `print` command which could return a
number using scientific notation like `1.60459e+10` and when ruby
converts it to an integer it will have the value of `1` instead of
`16045879296`. Which means even though you have 16GB of free space you
could not upload a 1GB backup file.

This commit uses the `printf` command instead which allows you to
specify that you do not want scientific notation.

I'm not sure why this hasn't been an issue before, but I was
experiencing it locally in development.
2019-12-11 12:57:03 +11:00
..
assets DEV: lint file 2019-12-11 10:48:58 +11:00
controllers FIX: Prevent scientific notation in free space check (#8473) 2019-12-11 12:57:03 +11:00
helpers DEV: s/\$redis/Discourse\.redis (#8431) 2019-12-03 10:05:53 +01:00
jobs DEV: update rubocop to version 0.77 2019-12-10 11:48:39 +11:00
mailers DEV: s/\$redis/Discourse\.redis (#8431) 2019-12-03 10:05:53 +01:00
models DEV: update rubocop to version 0.77 2019-12-10 11:48:39 +11:00
serializers FIX: Muted tags are respected by TopicTrackingState (#8467) 2019-12-10 09:50:05 +11:00
services DEV: update rubocop to version 0.77 2019-12-10 11:48:39 +11:00
views FEATURE: improve email change workflow 2019-11-21 16:28:35 +11:00