Bas Zalmstra
Bas Zalmstra
> Progress report is not the best, as messages such as `fetching repodata for environment` can end up being displayed a fair few times. Is there a way to make...
Yeah that sounds fair! 👍
Rattler-build has a custom implementation here: https://github.com/prefix-dev/rattler-build/blob/a28628bc6d29e227dffc1a64c27fa5f0b50f7dc9/src/render/solver.rs#L136 Its not great but might serve as inspiration!
I can no longer reproduce this, probably due to some optimizations in the solver (there were many) I ran the following command to verify this: ```shell rattler create --dry-run -c...
I ran into this as well. I think it has something to do with `flatten`. See https://www.rustexplorer.com/b/uspq0k for a minimal reproducible case.
As far as I understand, old commits (before #512) still contain references to LFS. We would have to rewrite the entire history to completely get rid of that which would...
Yeah, we are aware but simply didn't want to rewrite history. Should we close this issue for now and reopen when it becomes a problem?
@jaimergp Do you have a suggestion on how we could "fix" this without having to rewrite all history? @jezdez Is this a serious problem we have to tackle before graduating?
Does setting a new ulimit work though @gftabor ? `ulimit -n 2048`?
I made a PR so that pixi tries to update the limit to 2048 at startup (it used to be 1024).