Ed Morley

Results 240 issues of Ed Morley

`dj_database_url.config` takes an `env` option that allows for customising the env var used for the database URL away from the default of `DATABASE_URL`: https://github.com/jazzband/dj-database-url/blob/7906f3bf800105e6ab33bfbf44e6863fd178295a/dj_database_url/__init__.py#L65-L66 However, this option isn't documented in...

Modern Pip (v9.0.0+) supports `Requires-Python` and so automatically takes the current Python version into account, when determining the latest version of packages that can be installed. As such, for modern...

### Summary The Buildpack API v0.10 spec says that the `CNB_TARGET_ARCH` and `CNB_TARGET_OS` env vars will always be set: https://github.com/buildpacks/spec/blob/buildpack/v0.10/buildpack.md#targets However, this is not the case iff the Platform API...

type/bug
status/triage

### Description Currently the Pack CLI's known builders list contains the following suggested Paketo builders: https://github.com/buildpacks/pack/blob/ce8db3c5d11b8e040fd565632668a697e53e4f87/internal/builder/known_builder.go#L40-L67 The descriptions for the builders defined in this repo (which are used when offline...

type/enhancement
status/discussion-needed

### Description Currently the Pack CLI's suggested builders list contains an outdated Google builder image, `gcr.io/buildpacks/builder:v1`, which is based on the EOL Ubuntu 18.04 LTS: https://github.com/buildpacks/pack/blob/ce8db3c5d11b8e040fd565632668a697e53e4f87/internal/builder/known_builder.go#L12-L18 ### Proposed solution -...

type/bug
status/ready

### Summary The `pack build` command is not correctly treating builders as trusted after #2043. Specifically, if a builder is "trusted but not suggested" then `pack build` treats it as...

type/bug
status/ready

Heroku itself currently runs on AMD64 CPUs, however, some users use our buildpacks locally on machines with ARM64 CPUs (such as M1/M2/M3 MacBooks) with the Heroku base images published to...

enhancement

This buildpack compiles jemalloc during the build and caches the result under a stack and jemalloc-specific path: https://github.com/gaffneyc/heroku-buildpack-jemalloc/blob/a7fe9271f64c861debe9b6cc814203c17e7e68dc/bin/compile#L37-L38 This correctly ensures that a recompile happens if the stack or requested...

Heroku-24 was released yesterday: https://devcenter.heroku.com/changelog-items/2898 Using this buildpack on Heroku-24 currently results in this error: ``` -----> Puppeteer app detected -----> Detected Stack changes, flushing cache -----> Updating apt caches...

To reduce the chance of intermittent failures like: ``` [Heroku Node.js Engine Buildpack] [Checking Node.js version] Detected Node.js version range: >=20.0.0

enhancement