jiebi/CodeConvo huggingface dataset:
Code change:
<!-- Note that these are hard requirements --<!-- You can use the "Go to file" functionality on GitHub to find the package Then you can go to the history for this package Find the latest "packagename: oldversion -newversion" commit The "newversion" is the current version of the package --- <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- name: blender <!-- The current version can be found easily with the same process as above for checking the master branch If an open PR is present for the package, take this version as the current one and link to the PR --current version: 2.93.5 desired version: 3.1 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Please tag this issue in your PR.

Related discussion:
text: --replace '${"$"}{LIBDIR}/opencollada'  '${opencollada}'  --replace '${"$"}{PYTHON_LIBPATH}/site-packages/numpy'  <del> '${python39Packages.numpy}/${python.sitePackages}/numpy' </del> <ins> '${python310Packages.numpy}/${python.sitePackages}/numpy' </ins> '' else '' substituteInPlace extern/clew/src/clew.c --replace '"libOpenCL.so"' '"${ocl-icd}/lib/libOpenCL.so"' '');
Code change:
<!-- Note that these are hard requirements --<!-- You can use the "Go to file" functionality on GitHub to find the package Then you can go to the history for this package Find the latest "packagename: oldversion -newversion" commit The "newversion" is the current version of the package --- <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- name: blender <!-- The current version can be found easily with the same process as above for checking the master branch If an open PR is present for the package, take this version as the current one and link to the PR --current version: 2.93.5 desired version: 3.1 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Please tag this issue in your PR.

Related discussion:
text: "-DPYTHON_VERSION=${python.pythonVersion}" "-DWITH_PYTHON_INSTALL=OFF" "-DWITH_PYTHON_INSTALL_NUMPY=OFF" <del> "-DPYTHON_NUMPY_PATH=${python39Packages.numpy}/${python.sitePackages}" "-DPYTHON_NUMPY_INCLUDE_DIRS=${python39Packages.numpy}/${python.sitePackages}/numpy/core/include" </del> <ins> "-DPYTHON_NUMPY_PATH=${python310Packages.numpy}/${python.sitePackages}" "-DPYTHON_NUMPY_INCLUDE_DIRS=${python310Packages.numpy}/${python.sitePackages}/numpy/core/include" </ins> "-DWITH_PYTHON_INSTALL_REQUESTS=OFF" "-DWITH_OPENVDB=ON" "-DWITH_TBB=ON"
Code change:
Qtile is missing all the ffi modules so one can't use the pulse widget Just install qtile and add a To the config There is a script that has to be run as part of the packaging process takes care of creating the ffi modules, not sure if that will be enough or patching to change the paths will also be required.
Problem still here, and only for this module

Related discussion:
text: <del> { config, lib, pkgs, ... }: </del> <ins> { config, pkgs, lib, ... }: </ins> with lib; let cfg = config.services.xserver.windowManager.qtile; <ins> pyEnv = pkgs.python3.withPackages (p: [ (cfg.package.unwrapped or cfg.package) ] ++ (cfg.extraPackages p)); </ins> in { options.services.xserver.windowManager.qtile = { enable = mkEnableOption (lib.mdDoc "qtile"); <del> package = mkPackageOptionMD pkgs "qtile" { }; </del> <ins> package = mkPackageOptionMD pkgs "qtile-unwrapped" { }; configFile = mkOption { type = with types; nullOr path; default = null; example = literalExpression "./your_config.py"; description = lib.mdDoc '' Path to the qtile configuration file. If null, $XDG_CONFIG_HOME/qtile/config.py will be used. ''; }; backend = mkOption { type = types.enum [ "x11" "wayland" ]; default = "x11"; description = lib.mdDoc '' Backend to use in qtile: <option>x11</option> or <option>wayland</option>. ''; }; extraPackages = mkOption { type = types.functionTo (types.listOf types.package); default = _: []; defaultText = literalExpression '' python3Packages: with python3Packages; []; ''; description = lib.mdDoc '' Extra Python packages available to Qtile. An example would be to include `python3Packages.qtile-extras` for additional unoffical widgets. ''; example = literalExpression '' python3Packages: with python3Packages; [ qtile-extras ]; ''; }; </ins> }; config = mkIf cfg.enable { services.xserver.windowManager.session = [{ name = "qtile"; start = '' <del> ${cfg.package}/bin/qtile start & </del> <ins> ${pyEnv}/bin/qtile start -b ${cfg.backend}  ${optionalString (cfg.configFile != null) "--config "${cfg.configFile}""} & </ins> waitPID=$! ''; }];
Code change:
Qtile is missing all the ffi modules so one can't use the pulse widget Just install qtile and add a To the config There is a script that has to be run as part of the packaging process takes care of creating the ffi modules, not sure if that will be enough or patching to change the paths will also be required.
Problem still here, and only for this module

Related discussion:
text: <ins> { python3, qtile-unwrapped }: (python3.withPackages (_: [ qtile-unwrapped ])).overrideAttrs (_: { # otherwise will be exported as "env", this restores `nix search` behavior name = "${qtile-unwrapped.pname}-${qtile-unwrapped.version}"; # export underlying qtile package passthru = { unwrapped = qtile-unwrapped; }; # restore original qtile attrs inherit (qtile-unwrapped) pname version meta; }) </ins>
Code change:
Qtile is missing all the ffi modules so one can't use the pulse widget Just install qtile and add a To the config There is a script that has to be run as part of the packaging process takes care of creating the ffi modules, not sure if that will be enough or patching to change the paths will also be required.
Problem still here, and only for this module

Related discussion:
text: , xorgserver , pulseaudio , pytest-asyncio <del> , qtile </del> <ins> , qtile-unwrapped </ins> , keyring , requests , stravalib
Code change:
Qtile is missing all the ffi modules so one can't use the pulse widget Just install qtile and add a To the config There is a script that has to be run as part of the packaging process takes care of creating the ffi modules, not sure if that will be enough or patching to change the paths will also be required.
Problem still here, and only for this module

Related discussion:
text: ]; checkInputs = [ pytest-asyncio <del> qtile.unwrapped </del> <ins> qtile-unwrapped </ins> pulseaudio keyring requests
Code change:
Qtile is missing all the ffi modules so one can't use the pulse widget Just install qtile and add a To the config There is a script that has to be run as part of the packaging process takes care of creating the ffi modules, not sure if that will be enough or patching to change the paths will also be required.
Problem still here, and only for this module

Related discussion:
text: qpdfview = libsForQt5.callPackage ../applications/office/qpdfview { }; <del> qtile = callPackage ../applications/window-managers/qtile { }; </del> <ins> qtile-unwrapped = callPackage ../applications/window-managers/qtile { }; qtile = callPackage ../applications/window-managers/qtile/wrapper.nix { }; </ins> vimgolf = callPackage ../games/vimgolf { };
Code change:
Obsidian is unable to run (non-nixpkgs) git commands, due to being prefixed with . Steps to reproduce the behavior: non-nixpkgs from nixpkgs in obsidian the command Git syncing properly <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
Why don't you use git from nixpkgs (e.g. )?
That does work, although I'd prefer not to install git with on manjaro. I have other workaround that i use, i simply wanted to report how seem to break subcommands.
Just updated, and this also affects electron 16
We could consider prepending to in the derivation (the start script in the output).
can you guesstimate how many percent of obsidian users have obsidian-git plugin installed?
Of all obsidian users: few. Of obsidian&cap;nixpkgs users: maybe 20%?
Possibly related:
can you please check whether the fix in fixes this issue for you?
Seems to work!

Related discussion:
text: electronLibPath = with lib; makeLibraryPath ( [ libuuid at-spi2-atk at-spi2-core libappindicator-gtk3 ] ++ optionals (versionAtLeast version "9.0.0") [ libdrm mesa ] <ins> ++ optionals (versionOlder version "10.0.0") [ libXScrnSaver ] </ins> ++ optionals (versionAtLeast version "11.0.0") [ libxkbcommon ] ++ optionals (versionAtLeast version "12.0.0") [ libxshmfence ] ++ optionals (versionAtLeast version "17.0.0") [ libglvnd ]
Code change:
Obsidian is unable to run (non-nixpkgs) git commands, due to being prefixed with . Steps to reproduce the behavior: non-nixpkgs from nixpkgs in obsidian the command Git syncing properly <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
Why don't you use git from nixpkgs (e.g. )?
That does work, although I'd prefer not to install git with on manjaro. I have other workaround that i use, i simply wanted to report how seem to break subcommands.
Just updated, and this also affects electron 16
We could consider prepending to in the derivation (the start script in the output).
can you guesstimate how many percent of obsidian users have obsidian-git plugin installed?
Of all obsidian users: few. Of obsidian&cap;nixpkgs users: maybe 20%?
Possibly related:
can you please check whether the fix in fixes this issue for you?
Seems to work!

Related discussion:
text: $out/lib/electron/electron  ${lib.optionalString (lib.versionAtLeast version "15.0.0") "$out/lib/electron/chrome_crashpad_handler" } <del> wrapProgram $out/lib/electron/electron  --prefix LD_PRELOAD : ${lib.makeLibraryPath [ libXScrnSaver ]}/libXss.so.1  "''${gappsWrapperArgs[@]}" </del> <ins> wrapProgram $out/lib/electron/electron "''${gappsWrapperArgs[@]}" </ins> ''; };
Code change:
Password hashes, while less sensitive than unhashed passwords, are secrets. We should therefore have a option in that avoids both placing the hashes in the store world-readable and storing the password unhashed.
This is a common misunderstanding due to the bad naming of these options: → string of plaintext password → string of password hash → file containing password hash So, what you want already exists and it's .
Oh wow, indeed. Thanks! Given that the option is named so confusingly and that its description starts with "The full path to a file that contains the user's password." I think we should keep the issue, pending an option rename and a documentation improvement.

Related discussion:
text: - `getent` has been moved from `glibc`'s `bin` output to its own dedicated output, reducing closure size for many dependents. Dependents using the `getent` alias should not be affected; others should move from using `glibc.bin` or `getBin glibc` to `getent` (which also improves compatibility with non-glibc platforms). <ins> - The `users.users.<name>.passwordFile` has been renamed to `users.users.<name>.hashedPasswordFile` to avoid possible confusions. The option is in fact the file-based version of `hashedPassword`, not `password`, and expects a file containing the {manpage}`crypt(3)` hash of the user password. </ins> - The `services.ananicy.extraRules` option now has the type of `listOf attrs` instead of `string`. - The `matrix-synapse` package & module have undergone some significant internal changes, for most setups no intervention is needed, though:
Code change:
Password hashes, while less sensitive than unhashed passwords, are secrets. We should therefore have a option in that avoids both placing the hashes in the store world-readable and storing the password unhashed.
This is a common misunderstanding due to the bad naming of these options: → string of plaintext password → string of password hash → file containing password hash So, what you want already exists and it's .
Oh wow, indeed. Thanks! Given that the option is named so confusingly and that its description starts with "The full path to a file that contains the user's password." I think we should keep the issue, pending an option rename and a documentation improvement.

Related discussion:
text: passwordDescription = '' The options {option}`hashedPassword`, <del> {option}`password` and {option}`passwordFile` </del> <ins> {option}`password` and {option}`hashedPasswordFile` </ins> controls what password is set for the user. {option}`hashedPassword` overrides both <del> {option}`password` and {option}`passwordFile`. {option}`password` overrides {option}`passwordFile`. </del> <ins> {option}`password` and {option}`hashedPasswordFile`. {option}`password` overrides {option}`hashedPasswordFile`. </ins> If none of these three options are set, no password is assigned to the user, and the user will not be able to do password logins. If the option {option}`users.mutableUsers` is true, the
Code change:
Password hashes, while less sensitive than unhashed passwords, are secrets. We should therefore have a option in that avoids both placing the hashes in the store world-readable and storing the password unhashed.
This is a common misunderstanding due to the bad naming of these options: → string of plaintext password → string of password hash → file containing password hash So, what you want already exists and it's .
Oh wow, indeed. Thanks! Given that the option is named so confusingly and that its description starts with "The full path to a file that contains the user's password." I think we should keep the issue, pending an option rename and a documentation improvement.

Related discussion:
text: ''; }; <del> passwordFile = mkOption { </del> <ins> hashedPasswordFile = mkOption { </ins> type = with types; nullOr str; <del> default = null; </del> <ins> default = cfg.users.${name}.passwordFile; defaultText = literalExpression "null"; </ins> description = lib.mdDoc '' <del> The full path to a file that contains the user's password. The password file is read on each system activation. The file should contain exactly one line, which should be the password in an encrypted form that is suitable for the `chpasswd -e` command. </del> <ins> The full path to a file that contains the hash of the user's password. The password file is read on each system activation. The file should contain exactly one line, which should be the password in an encrypted form that is suitable for the `chpasswd -e` command. </ins> ${passwordDescription} ''; }; <ins> passwordFile = mkOption { type = with types; nullOr (passwdEntry str); default = null; visible = false; description = lib.mdDoc "Deprecated alias of hashedPasswordFile"; }; </ins> initialHashedPassword = mkOption { type = with types; nullOr (passwdEntry str); default = null;
Code change:
Password hashes, while less sensitive than unhashed passwords, are secrets. We should therefore have a option in that avoids both placing the hashes in the store world-readable and storing the password unhashed.
This is a common misunderstanding due to the bad naming of these options: → string of plaintext password → string of password hash → file containing password hash So, what you want already exists and it's .
Oh wow, indeed. Thanks! Given that the option is named so confusingly and that its description starts with "The full path to a file that contains the user's password." I think we should keep the issue, pending an option rename and a documentation improvement.

Related discussion:
text: users = mapAttrsToList (_: u: { inherit (u) name uid group description home homeMode createHome isSystemUser <del> password passwordFile hashedPassword </del> <ins> password hashedPasswordFile hashedPassword </ins> autoSubUidGidRange subUidRanges subGidRanges initialPassword initialHashedPassword expires; shell = utils.toShellPath u.shell;
Code change:
Password hashes, while less sensitive than unhashed passwords, are secrets. We should therefore have a option in that avoids both placing the hashes in the store world-readable and storing the password unhashed.
This is a common misunderstanding due to the bad naming of these options: → string of plaintext password → string of password hash → file containing password hash So, what you want already exists and it's .
Oh wow, indeed. Thanks! Given that the option is named so confusingly and that its description starts with "The full path to a file that contains the user's password." I think we should keep the issue, pending an option rename and a documentation improvement.

Related discussion:
text: && (allowsLogin cfg.hashedPassword || cfg.password != null <del> || cfg.passwordFile != null </del> <ins> || cfg.hashedPasswordFile != null </ins> || cfg.openssh.authorizedKeys.keys != [] || cfg.openssh.authorizedKeys.keyFiles != []) ) cfg.users ++ [
Code change:
Password hashes, while less sensitive than unhashed passwords, are secrets. We should therefore have a option in that avoids both placing the hashes in the store world-readable and storing the password unhashed.
This is a common misunderstanding due to the bad naming of these options: → string of plaintext password → string of password hash → file containing password hash So, what you want already exists and it's .
Oh wow, indeed. Thanks! Given that the option is named so confusingly and that its description starts with "The full path to a file that contains the user's password." I think we should keep the issue, pending an option rename and a documentation improvement.

Related discussion:
text: The password hash of user "${user.name}" may be invalid. You must set a valid hash or the user will be locked out of their account. Please check the value of option `users.users."${user.name}".hashedPassword`.'' <del> else null )); </del> <ins> else null) ++ flip mapAttrsToList cfg.users (name: user: if user.passwordFile != null then ''The option `users.users."${name}".passwordFile' has been renamed '' + ''to `users.users."${name}".hashedPasswordFile'.'' else null) ); </ins> }; }
Code change:
yaru-theme fails to build on the latest nixos-unstable Steps to reproduce the behavior: fails Buiild succeeds ! `

Related discussion:
text: stdenv.mkDerivation rec { pname = "yaru"; <del> version = "22.04.3.1"; </del> <ins> version = "unstable-2022-04-07"; # 22.04.3.1 is broken </ins> src = fetchFromGitHub { owner = "ubuntu"; repo = "yaru"; <del> rev = version; sha256 = "sha256-nNI6Nm3ZpIJRTbIbe/P9cKofcthb6qWKjn81/ZpPo2g="; </del> <ins> rev = "9bdbf66bf3718c6595c7a15ef4698ba471a36526"; sha256 = "02f6m0jxnsczw3y7v7bqdihxa33sx2z93yn3j8w4z9r9fv2pn06b"; </ins> }; nativeBuildInputs = [ meson sassc pkg-config glib ninja python3 ]; buildInputs = [ gtk3 gnome.gnome-themes-extra ]; propagatedBuildInputs = [ humanity-icon-theme hicolor-icon-theme ]; propagatedUserEnvPkgs = [ gtk-engine-murrine ]; dontDropIconThemeCache = true;
Code change:
QEMU VMs using the profile that have a in their hostname were broken by A clear and concise description of what you expected to happen. If applicable, add screenshots to help explain your problem. Add any other context about the problem here. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result.

Related discussion:
text: (mkIf (pkgs.stdenv.isAarch32 || pkgs.stdenv.isAarch64) [ "-device virtio-gpu-pci" "-device usb-ehci,id=usb0" "-device usb-kbd" "-device usb-tablet" ]) <del> (mkIf (!cfg.useBootLoader) [ "-kernel ${NIXPKGS_QEMU_KERNEL_${config.system.name}:-${config.system.build.toplevel}/kernel}" </del> <ins> (let alphaNumericChars = lowerChars ++ upperChars ++ (map toString (range 0 9)); # Replace all non-alphanumeric characters with underscores sanitizeShellIdent = s: concatMapStrings (c: if builtins.elem c alphaNumericChars then c else "_") (stringToCharacters s); in mkIf (!cfg.useBootLoader) [ "-kernel ${NIXPKGS_QEMU_KERNEL_${sanitizeShellIdent config.system.name}:-${config.system.build.toplevel}/kernel}" </ins> "-initrd ${config.system.build.toplevel}/initrd" ''-append "$(cat ${config.system.build.toplevel}/kernel-params) init=${config.system.build.toplevel}/init regInfo=${regInfo}/registration ${consoles} $QEMU_KERNEL_PARAMS"'' ])
Code change:
, CVSSv3=7.5 (nixos-unstable) Vyper is a Pythonic Smart Contract Language for the Ethereum Virtual Machine. In version 0.3.1 and prior, bytestrings can have dirty bytes in them, resulting in the word-for-word comparisons giving incorrect results. Even without dirty nonzero bytes, two bytestrings can compare to equal if one ends with because there is no comparison of the length. A patch is available and expected to be part of the 0.3.2 release. There are currently no known workarounds. Scanned versions: nixos-unstable: . Cc

Related discussion:
text: , buildPythonPackage , fetchPypi , pythonOlder <del> , pythonAtLeast </del> , pythonRelaxDepsHook , writeText , asttokens
Code change:
, CVSSv3=7.5 (nixos-unstable) Vyper is a Pythonic Smart Contract Language for the Ethereum Virtual Machine. In version 0.3.1 and prior, bytestrings can have dirty bytes in them, resulting in the word-for-word comparisons giving incorrect results. Even without dirty nonzero bytes, two bytestrings can compare to equal if one ends with because there is no comparison of the length. A patch is available and expected to be part of the 0.3.2 release. There are currently no known workarounds. Scanned versions: nixos-unstable: . Cc

Related discussion:
text: , sphinx_rtd_theme , pytest-runner , setuptools-scm <ins> , git </ins> }: let
Code change:
, CVSSv3=7.5 (nixos-unstable) Vyper is a Pythonic Smart Contract Language for the Ethereum Virtual Machine. In version 0.3.1 and prior, bytestrings can have dirty bytes in them, resulting in the word-for-word comparisons giving incorrect results. Even without dirty nonzero bytes, two bytestrings can compare to equal if one ends with because there is no comparison of the length. A patch is available and expected to be part of the 0.3.2 release. There are currently no known workarounds. Scanned versions: nixos-unstable: . Cc

Related discussion:
text: in buildPythonPackage rec { pname = "vyper"; <del> version = "0.3.1"; </del> <ins> version = "0.3.3"; </ins> format = "setuptools"; <del> disabled = pythonOlder "3.7" || pythonAtLeast "3.10"; </del> <ins> disabled = pythonOlder "3.7"; </ins> src = fetchPypi { inherit pname version; <del> sha256 = "sha256-fXug5v3zstz19uexMWokHBVsfcl2ZCdIOIXKeLVyh/Q="; </del> <ins> sha256 = "sha256-BAnNj27B1HAb9VVDA69bFGbQjeOpl0g5EB2juajqBAw="; </ins> }; nativeBuildInputs = [ <ins> # Git is used in setup.py to compute version information during building # ever since https://github.com/vyperlang/vyper/pull/2816 git </ins> pythonRelaxDepsHook pytest-runner setuptools-scm