Claudio Bartoli

> > > From my experience the most common scenario for why you'd want to pin a package version is when there is a known issue with a newer version...

By default `pipenv` update `Pipfile.lock` file if it's out of date. On ci environment I don't want this default behaviour but I need exacly dependencies. Additional details can be found...

> Don't use the `pipenv-fork` documentation, its not our current documentation, which can be found at: https://pipenv.pypa.io/en/latest/ Sorry, fast google search results, I've update the comment with the right reference....

Just tried, bust the real focus of the issue was not dependencies install but script executions. On single purpose containers I try to avoid venvs in order to limit encapsulation...

Solved installing package `procps`. I have figured out that on *nix package an additional package `procps` is required and can be installed with: ```bash # debian/ubuntu based distro $ [sudo]...

I had a similar issue with the `vitepress-plugin-mermaid` addon. I've solved creating a theme file in `.vitepress/theme/index.ts` as [documented](https://vitepress.dev/guide/custom-theme). I don't need a particular theme so I've just extended the...

Same issue here: I'm trying to setup storybook tests that requires a live webserver during the test process. ``` jsonc { // ... "scripts": { "test:sb": "run-p --race --print-label test:sb:*",...

Solved installing package `procps`. I have figured out that on *nix package an additional package `procps` is required and can be installed with: ```bash # debian/ubuntu based distro $ [sudo]...

Yup, it works like a charm.

> Just to clarify, is every mention of `poetry` a typo that should have been `pyenv`? (I assume yes) Yes, I'm hitting the same issue. Just replace any `poetry` with...