Tags: changsongyang/devbox
Tags
Bump version to 0.14.0 (jetify-com#2515) ## Summary Bump to version 0.14.0 ## How was it tested? Confirmed via `nix build .` on localhost --------- Signed-off-by: John Lago <750845+Lagoja@users.noreply.github.com>
fix: disable poetry plugin output (jetify-com#2482) ## Summary When using poetry, with the suggested `init_hook` from the docs: ``` { "packages": [ "python3", "poetry@1.8" // notice I am using poetry 1.8, the poetry shell command is not part of poetry version 2.0 ], "shell": { "init_hook": "poetry shell" } } ``` and running `devbox shell`, while the poetry env is being loaded, it generates this log: `Using virtualenv: /home/fotiadis/src/work/trumo/services/tc_gateway_consumer/.venv` This can be problematic to users instant prompt like the very famous zsh theme [powerlevel10k](https://github.com/romkatv/powerlevel10k) By adding the `--quiet` flag this solves the problem ### What about poetry 2.0? poetry 2.0 has removed the `poetry shell` (the functionality still exists if you download a plugin). The new way to achieve the same behavior according to [the docs](https://python-poetry.org/docs/managing-environments/#activating-the-environment) is: `eval $(poetry env activate)` This change doesn't impact either major versions of poetry, and it will continue to work as normal ## How was it tested? By disabling the current poetry plugin, and creating a new one that is the exact copy, just with the flag on
fix: disable poetry plugin output (jetify-com#2482) ## Summary When using poetry, with the suggested `init_hook` from the docs: ``` { "packages": [ "python3", "poetry@1.8" // notice I am using poetry 1.8, the poetry shell command is not part of poetry version 2.0 ], "shell": { "init_hook": "poetry shell" } } ``` and running `devbox shell`, while the poetry env is being loaded, it generates this log: `Using virtualenv: /home/fotiadis/src/work/trumo/services/tc_gateway_consumer/.venv` This can be problematic to users instant prompt like the very famous zsh theme [powerlevel10k](https://github.com/romkatv/powerlevel10k) By adding the `--quiet` flag this solves the problem ### What about poetry 2.0? poetry 2.0 has removed the `poetry shell` (the functionality still exists if you download a plugin). The new way to achieve the same behavior according to [the docs](https://python-poetry.org/docs/managing-environments/#activating-the-environment) is: `eval $(poetry env activate)` This change doesn't impact either major versions of poetry, and it will continue to work as normal ## How was it tested? By disabling the current poetry plugin, and creating a new one that is the exact copy, just with the flag on
patchpkg: fix system CUDA lib search (jetify-com#2507) As part of the auto-patching for CUDA, devbox searches for the system's libcuda (installed by the driver) and adds it to the Nix store. This fixes a couple of bugs with that search process: - When creating the soname links, the base name of the path to libcuda wasn't being used. This would lead to creating symlinks like "lib/libcuda.so.1", which would fail because a lib subdirectory didn't exist. - Ensure the `src` attribute is set in the patch flake so that devbox knows the path the flake source (which contains the copied libcuda) at build time.
[docs] add note about github plugin cache env-var (jetify-com#2479) ## Summary ## How was it tested?
[docs] add note about github plugin cache env-var (jetify-com#2479) ## Summary ## How was it tested?
nix: make internal/nix.cmd public (jetify-com#2473) Move `internal/nix.cmd` and friends to the top-level nix package and export it. The constructor function is now a `Nix.Command` method. New commands use `Nix.Logger` for debug logs and include default arguments from `Nix.ExtraArgs`. As a convenience, the package-level `Command` function calls `Default.Command` (which uses the default Nix installation found in $PATH).
nix: make internal/nix.cmd public (jetify-com#2473) Move `internal/nix.cmd` and friends to the top-level nix package and export it. The constructor function is now a `Nix.Command` method. New commands use `Nix.Logger` for debug logs and include default arguments from `Nix.ExtraArgs`. As a convenience, the package-level `Command` function calls `Default.Command` (which uses the default Nix installation found in $PATH).
nix/flake: fix Ref.String() for github flakes w/ rev and ref (jetify-… …com#2467) The string form of GitHub flakeref can only have a rev or a ref, not both. For example: - Good: `github:NixOS/nixpkgs/b321c8e818546d5491ee5611476500557b880856` - Good: `github:NixOS/nixpkgs/nixpkgs-unstable` - Bad: `github:NixOS/nixpkgs/nixpkgs-unstable/b321c8e818546d5491ee5611476500557b880856` If both the Rev and Ref fields are set, use Rev.
nix/flake: fix Ref.String() for github flakes w/ rev and ref (jetify-… …com#2467) The string form of GitHub flakeref can only have a rev or a ref, not both. For example: - Good: `github:NixOS/nixpkgs/b321c8e818546d5491ee5611476500557b880856` - Good: `github:NixOS/nixpkgs/nixpkgs-unstable` - Bad: `github:NixOS/nixpkgs/nixpkgs-unstable/b321c8e818546d5491ee5611476500557b880856` If both the Rev and Ref fields are set, use Rev.
PreviousNext