BUGFIX: Fix rounding issues due to ramOverride edge cases (#1339)

*All* RAM calculations must take place in units of hundredths-of-a-GB in
order for there not to be issues.

Also adds slightly more verbose logging when the dynamic RAM check
fails.
This commit is contained in:
David Walker
2024-06-28 17:58:17 -07:00
committed by GitHub
parent 357cc568e9
commit 06d742a7f3
5 changed files with 12 additions and 4 deletions

View File

@@ -270,7 +270,8 @@ interface RunOptions {
* You can also use this to <i>increase</i> the RAM if the static RAM checker has missed functions
* that you need to call.
*
* Must be greater-or-equal to the base RAM cost. Defaults to the statically calculated cost.
* Must be greater-or-equal to the base RAM cost. Will be rounded to the nearest hundredth-of-a-GB,
* which is the granularity of all RAM calculations. Defaults to the statically calculated cost.
*/
ramOverride?: number;
/**