Capi Etheriel

fwiw, i went with flox.dev too. the [layering environments](https://flox.dev/docs/tutorials/layering-multiple-environments/) feature made me realize all I needed was a single layer with the tools -- leave the actual shell to the...

those are not errors. it looks like somewhere in your scripts you've set up tracing (`set -c` or `set -o xtrace`) or maybe verbose (`set -v` or `set -o verbose`).

FWIW ci passes in my repo: https://github.com/barraponto/golevelup-nestjs/actions/runs/10532889002?pr=1 (although integration tests seem to blow up, it passes anyway)

Something needs to be configured because this PR removes node 19 support, but github actions is still expecting it...

Upon learning of the existence of `flox activate --mode run`, I intuitively ran `flox help activate` and it did work 🥳 I do notice, however, that `flox help` is not...

As a long time linux and shell user, i'm very aware that `ctrl+d` is enough to exit the flox subshell. I wouldn't mind having a `flox deactivate` command to exit...

I solved it _in this specific case_ by subclassing from Session: ```python class ContactsDB(Session): pass @contextmanager def create_contacts_db() -> Iterator[Session]: engine = create_engine("sqlite:///data/wa.db") with ContactsDB(engine) as session: yield session registry.register_factory(ContactsDB,...

Just wanted to highlight that the suggestion from the documentation, wrapping the value in `str`, breaks the opposite use case (using the alias): ```python from pydantic import BaseModel, ConfigDict, Field...

fwiw, when it shows the warning, it actually displays my username. ``` cannot determine effective uid - continuing as user 'barraponto', ```

nah, it works fine. haven't noticed any issue so far.