-
Jose Diaz-Gonzalez authored
* fix: handle case where memory.limit_in_bytes is nonsensically large In certain CI environments, this value can be misreported, resulting in an invalid initial `MEMORY_AVAILABLE` value. In these cases, we default the max detected memory to 16GB, or slightly larger than a `performance-l` instance.
5a76f5f1
| Name |
Last commit
|
Last update |
|---|---|---|
| .github | ||
| bin | ||
| ci-profile | ||
| etc | ||
| lib | ||
| plugin | ||
| profile | ||
| spec | ||
| test | ||
| vendor | ||
| .gitignore | ||
| .travis.yml | ||
| CHANGELOG.md | ||
| Gemfile | ||
| Gemfile.lock | ||
| LICENSE | ||
| README.md | ||
| buildpack.toml | ||
| hatchet.json | ||
| makefile |