Ludovico Cavedon

It looks like that the code that expands ruby templates in configuration variables (i.e. when dymanic_values: true) [traverses](https://github.com/markround/tiller/blob/master/bin/tiller#L111) the configuration objects using [deep_traverse()](https://github.com/markround/tiller/blob/master/lib/tiller/util.rb#L18), which stops at lists.

> you should not use `poetry run` in your build script; or anyway definitely not without declaring `poetry` as a build requirement. > > just call `protoc` directly - that...

I do _not_ think this is a duplicate of #8749: - I tried to patch as suggested in https://github.com/python-poetry/poetry/issues/8749#issuecomment-1841516573, but it does not help. ``` index 3edb225c..47ecdc51 100644 --- a/src/poetry/inspection/info.py...

Setting `generate-setup-file = true` fails in a similar way: ``` % poetry build Preparing build environment with build-system requirements poetry-core, protoc-exe, setuptools Building mypoetrytest (0.1.0) A setup.py file already exists....

> I don't know what the right fix is but I'm pretty sure that it's not going to be what you suggest - updating `os.environ` looks horrid I agree, I...

> another approach would just not to try and do this via build requirements - there's at least a case that installing executables isn't really what build requirements are for...

Fixed by https://github.com/gin-gonic/gin/pull/3683

This should be now resolved in #9

> I configured two Docker clouds, one a copy of the other, and watched the allocation. As far as I could tell, it was always choosing the first cloud, whether...

@zanieb , my use case is running a tool (and only that tool with its dependencies) in an isolated venv at a version locked in uv.lock. For example, the tool...