Ed Morley

Since this appears to be a pip/docker caching issue + there was no reply, this can probably be closed out now?

As filed, this issue is now resolved since the Python 3.11 images now ship with pip 24.0: https://github.com/docker-library/python/blob/cc2cf19f2c9a440706d17b5937bf104052eef967/versions.json#L24-L32 ``` $ docker run -q --rm python:3.11-slim-bookworm pip --version pip 24.0 from...

This can presumably be closed out, given it was an outdated Docker issue? > it is the libseccomp (and docker and containerd) of the host that you need to update,...

I presume this issue can now be closed, since the base `buildpack-deps` image will have been updated several times since?

This would be a great feature. Is `RSpec.current_example.description` the correct way to access this metadata from within the matcher?

Something else I've just discovered - this issue only affects uWSGI when it was installed into the user site-packages using using `pip install --user`. If uWSGI was installed into the...

This was caused by: https://github.com/jupyterhub/jupyterhub/issues/4903 And will be fixed by: https://github.com/jupyterhub/jupyterhub/pull/4904

@jacobian, I'm happy to open a PR to fix this - just need to know which approach you'd prefer: (a) defaulting `proxy_header` to `None` (b) failing loudly if `proxy_header` is...

> I would recommend either: > > 1. Pulling in those changes into this repo. > > 2. Or, if you no longer wish to maintain this repo (now that...

@timshadel Hi! Thank you for the reply. People are already using https://github.com/heroku/heroku-buildpack-github-netrc and manual testing for the conversion from Ruby to bash was also performed in: https://github.com/heroku/heroku-buildpack-github-netrc/pull/3#issuecomment-1166486620 However, if you...