jiebi/CodeConvo huggingface dataset:
Code change:
The build fails in the test phase when CUDA is enabled with errors like this: Note that the did not have this problem. Steps to reproduce the behavior:
I've played around a little bit and couldn't get it working. The problems is that the CUDA drivers are available at runtime in but not in the cudatoolkit. I've symlinked and then the library is found but CUDA is not running properly in the sandbox (). I've looked around somewhat and neither Torch, nor Tensorflow, nor Numba, ... have CUDA tests running in their respective expressions. I would assume for exactly this reasons. I suggest to just disable the CUDA tests and have them running for CPU only.
That sounds reasonable.

Related discussion:
text: "-DOPENMM_BUILD_SHARED_LIB=ON" ] ++ lib.optionals enablePython [ "-DOPENMM_BUILD_PYTHON_WRAPPERS=ON" <del> ] ++ lib.optionals enableClang [ "-DCMAKE_C_COMPILER=${clang}/bin/clang" "-DCMAKE_CXX_COMPILER=${clang}/bin/clang++" </del> ] ++ lib.optionals enableOpencl [ "-DOPENMM_BUILD_OPENCL_LIB=ON" "-DOPENMM_BUILD_AMOEBA_OPENCL_LIB=ON" "-DOPENMM_BUILD_DRUDE_OPENCL_LIB=ON" "-DOPENMM_BUILD_RPMD_OPENCL_LIB=ON" ] ++ lib.optionals enableCuda [ <del> "-DCUDA_SDK_ROOT_DIR=${cudatoolkit}" </del> <ins> "-DCUDA_SDK_ROOT_DIR=${cudaPackages.cudatoolkit}" </ins> "-DOPENMM_BUILD_AMOEBA_CUDA_LIB=ON" "-DOPENMM_BUILD_CUDA_LIB=ON" "-DOPENMM_BUILD_DRUDE_CUDA_LIB=ON" "-DOPENMM_BUILD_RPMD_CUDA_LIB=ON" <del> "-DCMAKE_LIBRARY_PATH=${cudatoolkit}/lib64/stubs" </del> <ins> "-DCMAKE_LIBRARY_PATH=${cudaPackages.cudatoolkit}/lib64/stubs" </ins> ]; postInstall = lib.strings.optionalString enablePython '' <del> export OPENMM_LIB_PATH=$out/lib export OPENMM_INCLUDE_PATH=$out/include cd python ${python3Packages.python.interpreter} setup.py build ${python3Packages.python.interpreter} setup.py install --prefix=$out </del> <ins> export OPENMM_LIB_PATH=$out/lib export OPENMM_INCLUDE_PATH=$out/include cd python ${python3Packages.python.interpreter} setup.py build ${python3Packages.python.interpreter} setup.py install --prefix=$out ''; postFixup = '' for lib in $out/lib/plugins/*CUDA.so $out/lib/plugins/*Cuda*.so; do addOpenGLRunpath "$lib" done </ins> ''; <del> doCheck = true; </del> <ins> # Couldn't get CUDA to run properly in the sandbox doCheck = !enableCuda && !enableOpencl; </ins> meta = with lib; { description = "Toolkit for molecular simulation using high performance GPU code";
Code change:
Configuring airscan by writing to via silently does nothing, i. e. the file still has the default content. Steps to reproduce the behavior: airscan to sane backends: airscan, e. g. specific devices: After (or & reboot, etc) should contain This stopped working when upgrading from 22.05 to 22.11. I suspect the change to the module in is the root cause. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --I didn't find a entry in the sane module, so excuse me pinging the last few people who touched the module / were involved in the discussion of : Please run and paste the result.
Oh, sorry about that! I guess we can either point to somewhere else but , or figure out how to override using instead of ? As to why your config is ignored, does perhaps get ignored when is set? If so, that should probably be fixed.
Since this worked before, doesn't that mean airscan isn't using , and instead hardcodes ?
Using both and results in an error/warning at build time, but it doesn't prevent successful activation: Btw, you wrote (wrong order) in the first post :-)
You can use this workaround for now:
According to it's using the enviroment variable first, then falling back to . I guess that means in nixos 22.05 it was reading both the found in $SANECONFIGDIR (/nix/store/...) and then also I guess we can bring back the old behaviour by just pointing to or something instead of . Thoughts?
I made
Oops, I should start to copy paste this option, I always mess up the order That is a lot cleaner than what I came up with. Thanks. Wow, that was fast. Again, many thanks to you :)

Related discussion:
text: }; env = { <del> SANE_CONFIG_DIR = "/etc/sane.d"; </del> <ins> SANE_CONFIG_DIR = "/etc/sane-config"; </ins> LD_LIBRARY_PATH = [ "/etc/sane-libs" ]; };
Code change:
Configuring airscan by writing to via silently does nothing, i. e. the file still has the default content. Steps to reproduce the behavior: airscan to sane backends: airscan, e. g. specific devices: After (or & reboot, etc) should contain This stopped working when upgrading from 22.05 to 22.11. I suspect the change to the module in is the root cause. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --I didn't find a entry in the sane module, so excuse me pinging the last few people who touched the module / were involved in the discussion of : Please run and paste the result.
Oh, sorry about that! I guess we can either point to somewhere else but , or figure out how to override using instead of ? As to why your config is ignored, does perhaps get ignored when is set? If so, that should probably be fixed.
Since this worked before, doesn't that mean airscan isn't using , and instead hardcodes ?
Using both and results in an error/warning at build time, but it doesn't prevent successful activation: Btw, you wrote (wrong order) in the first post :-)
You can use this workaround for now:
According to it's using the enviroment variable first, then falling back to . I guess that means in nixos 22.05 it was reading both the found in $SANECONFIGDIR (/nix/store/...) and then also I guess we can bring back the old behaviour by just pointing to or something instead of . Thoughts?
I made
Oops, I should start to copy paste this option, I always mess up the order That is a lot cleaner than what I came up with. Thanks. Wow, that was fast. Again, many thanks to you :)

Related discussion:
text: environment.systemPackages = backends; environment.sessionVariables = env; <del> environment.etc."sane.d".source = config.hardware.sane.configDir; </del> <ins> environment.etc."sane-config".source = config.hardware.sane.configDir; </ins> environment.etc."sane-libs".source = "${saneConfig}/lib/sane"; services.udev.packages = backends;
Code change:
Building this package twice does not produce the bit-by-bit identical result each time, making it harder to detect CI breaches. You can read more about this at https://reproducible- . Fixing bit-by-bit reproducibility also has additional advantages, such as avoiding hard-to-reproduce bugs, making content-addressed storage more effective and reducing rebuilds in such systems. You can use to analyze the differences in the output of the two builds. To view the build log of the build that produced the artifact in the binary cache: Looks like symbol ordering differences:

Related discussion:
text: { lib, stdenv, fetchFromGitHub, cmake, gettext, msgpack, libtermkey, libiconv <ins> , fetchpatch </ins> , libuv, lua, ncurses, pkg-config , unibilium, gperf , libvterm-neovim
Code change:
Building this package twice does not produce the bit-by-bit identical result each time, making it harder to detect CI breaches. You can read more about this at https://reproducible- . Fixing bit-by-bit reproducibility also has additional advantages, such as avoiding hard-to-reproduce bugs, making content-addressed storage more effective and reducing rebuilds in such systems. You can use to analyze the differences in the output of the two builds. To view the build log of the build that produced the artifact in the binary cache: Looks like symbol ordering differences:

Related discussion:
text: nvim-client luv coxpcall busted luafilesystem penlight inspect ] )); <ins> codegenLua = if lua.pkgs.isLuaJIT then let deterministicLuajit = lua.override { deterministicStringIds = true; self = deterministicLuajit; }; in deterministicLuajit.withPackages(ps: [ ps.mpack ps.lpeg ]) else lua; </ins> pyEnv = python3.withPackages(ps: with ps; [ pynvim msgpack ]); in
Code change:
Building this package twice does not produce the bit-by-bit identical result each time, making it harder to detect CI breaches. You can read more about this at https://reproducible- . Fixing bit-by-bit reproducibility also has additional advantages, such as avoiding hard-to-reproduce bugs, making content-addressed storage more effective and reducing rebuilds in such systems. You can use to analyze the differences in the output of the two builds. To view the build log of the build that produced the artifact in the binary cache: Looks like symbol ordering differences:

Related discussion:
text: # necessary so that nix can handle `UpdateRemotePlugins` for the plugins # it installs. See https://github.com/neovim/neovim/issues/9413. ./system_rplugin_manifest.patch <ins> # make the build reproducible, rebased version of # https://github.com/neovim/neovim/pull/21586 (fetchpatch { name = "neovim-build-make-generated-source-files-reproducible.patch"; url = "https://github.com/raboof/neovim/commit/485dd2af3efbfd174163583c46e0bb2a01ff04f1.patch"; hash = "sha256-9aRVK4lDkL/W4RVjeKptrZFY7rYYBx6/RGR4bQSbCsM="; }) </ins> ]; dontFixCmake = true;
Code change:
Building this package twice does not produce the bit-by-bit identical result each time, making it harder to detect CI breaches. You can read more about this at https://reproducible- . Fixing bit-by-bit reproducibility also has additional advantages, such as avoiding hard-to-reproduce bugs, making content-addressed storage more effective and reducing rebuilds in such systems. You can use to analyze the differences in the output of the two builds. To view the build log of the build that produced the artifact in the binary cache: Looks like symbol ordering differences:

Related discussion:
text: substituteInPlace src/nvim/version.c --replace NVIM_VERSION_CFLAGS ""; ''; # check that the above patching actually works <del> disallowedReferences = [ stdenv.cc ]; </del> <ins> disallowedReferences = [ stdenv.cc ] ++ lib.optional (lua != codegenLua) codegenLua; </ins> cmakeFlags = [ # Don't use downloaded dependencies. At the end of the configurePhase one
Code change:
Building this package twice does not produce the bit-by-bit identical result each time, making it harder to detect CI breaches. You can read more about this at https://reproducible- . Fixing bit-by-bit reproducibility also has additional advantages, such as avoiding hard-to-reproduce bugs, making content-addressed storage more effective and reducing rebuilds in such systems. You can use to analyze the differences in the output of the two builds. To view the build log of the build that produced the artifact in the binary cache: Looks like symbol ordering differences:

Related discussion:
text: ++ lib.optional (!lua.pkgs.isLuaJIT) "-DPREFER_LUA=ON" ; <del> preConfigure = lib.optionalString stdenv.isDarwin '' </del> <ins> preConfigure = lib.optionalString lua.pkgs.isLuaJIT '' cmakeFlagsArray+=( "-DLUAC_PRG=${codegenLua}/bin/luajit -b -s %s -" "-DLUA_GEN_PRG=${codegenLua}/bin/luajit" ) '' + lib.optionalString stdenv.isDarwin '' </ins> substituteInPlace src/nvim/CMakeLists.txt --replace "    util" "" '';
Code change:
Building this package twice does not produce the bit-by-bit identical result each time, making it harder to detect CI breaches. You can read more about this at https://reproducible- . Fixing bit-by-bit reproducibility also has additional advantages, such as avoiding hard-to-reproduce bugs, making content-addressed storage more effective and reducing rebuilds in such systems. You can use to analyze the differences in the output of the two builds. To view the build log of the build that produced the artifact in the binary cache: Looks like symbol ordering differences:

Related discussion:
text: , enableAPICheck ? false , enableVMAssertions ? false , useSystemMalloc ? false <ins> # Upstream generates randomized string id's by default for security reasons # https://github.com/LuaJIT/LuaJIT/issues/626. Deterministic string id's should # never be needed for correctness (that should be fixed in the lua code), # but may be helpful when you want to embed jit-compiled raw lua blobs in # binaries that you want to be reproducible. , deterministicStringIds ? false </ins> , luaAttr ? "luajit_${lib.versions.major version}_${lib.versions.minor version}" } @ inputs: assert enableJITDebugModule -> enableJIT;
Code change:
Building this package twice does not produce the bit-by-bit identical result each time, making it harder to detect CI breaches. You can read more about this at https://reproducible- . Fixing bit-by-bit reproducibility also has additional advantages, such as avoiding hard-to-reproduce bugs, making content-addressed storage more effective and reducing rebuilds in such systems. You can use to analyze the differences in the output of the two builds. To view the build log of the build that produced the artifact in the binary cache: Looks like symbol ordering differences:

Related discussion:
text: ++ optional enableGDBJITSupport "-DLUAJIT_USE_GDBJIT" ++ optional enableAPICheck "-DLUAJIT_USE_APICHECK" ++ optional enableVMAssertions "-DLUAJIT_USE_ASSERT" <ins> ++ optional deterministicStringIds "-DLUAJIT_SECURITY_STRID=0" </ins> ; in stdenv.mkDerivation rec {
Code change:
Since which updated from 1.9.2 to 1.10.2, the scheduler service can't be started, the error reported in the logs is: Steps to reproduce the behavior: or to see error as above in the logs The service starts succesfully <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Module maintainers: Package maintainers: Please run and paste the result.
Probably fixed by

Related discussion:
text: ]; systemd.services.paperless-scheduler = { <del> description = "Paperless scheduler"; </del> <ins> description = "Paperless Celery Beat"; </ins> serviceConfig = defaultServiceConfig // { User = cfg.user; <del> ExecStart = "${pkg}/bin/paperless-ngx qcluster"; </del> <ins> ExecStart = "${pkg}/bin/celery --app paperless beat --loglevel INFO"; </ins> Restart = "on-failure"; <del> # The `mbind` syscall is needed for running the classifier. SystemCallFilter = defaultServiceConfig.SystemCallFilter ++ [ "mbind" ]; # Needs to talk to mail server for automated import rules PrivateNetwork = false; </del> }; environment = env; wantedBy = [ "multi-user.target" ]; <del> wants = [ "paperless-consumer.service" "paperless-web.service" ]; </del> <ins> wants = [ "paperless-consumer.service" "paperless-web.service" "paperless-task-queue.service" ]; </ins> preStart = '' ln -sf ${manage} ${cfg.dataDir}/paperless-manage
Code change:
Since which updated from 1.9.2 to 1.10.2, the scheduler service can't be started, the error reported in the logs is: Steps to reproduce the behavior: or to see error as above in the logs The service starts succesfully <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Module maintainers: Package maintainers: Please run and paste the result.
Probably fixed by

Related discussion:
text: after = [ "redis-paperless.service" ]; }; <ins> systemd.services.paperless-task-queue = { description = "Paperless Celery Workers"; serviceConfig = defaultServiceConfig // { User = cfg.user; ExecStart = "${pkg}/bin/celery --app paperless worker --loglevel INFO"; Restart = "on-failure"; # The `mbind` syscall is needed for running the classifier. SystemCallFilter = defaultServiceConfig.SystemCallFilter ++ [ "mbind" ]; # Needs to talk to mail server for automated import rules PrivateNetwork = false; }; environment = env; }; </ins> # Reading the user-provided password file requires root access systemd.services.paperless-copy-password = mkIf (cfg.passwordFile != null) { requiredBy = [ "paperless-scheduler.service" ];
Code change:
Since which updated from 1.9.2 to 1.10.2, the scheduler service can't be started, the error reported in the logs is: Steps to reproduce the behavior: or to see error as above in the logs The service starts succesfully <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Module maintainers: Package maintainers: Please run and paste the result.
Probably fixed by

Related discussion:
text: }; # Allow the web interface to access the private /tmp directory of the server. # This is required to support uploading files via the web interface. <del> unitConfig.JoinsNamespaceOf = "paperless-scheduler.service"; </del> <ins> unitConfig.JoinsNamespaceOf = "paperless-task-queue.service"; </ins> # Bind to `paperless-scheduler` so that the web server never runs # during migrations bindsTo = [ "paperless-scheduler.service" ];
Code change:
Since which updated from 1.9.2 to 1.10.2, the scheduler service can't be started, the error reported in the logs is: Steps to reproduce the behavior: or to see error as above in the logs The service starts succesfully <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Module maintainers: Package maintainers: Please run and paste the result.
Probably fixed by

Related discussion:
text: makeWrapper $out/lib/paperless-ngx/src/manage.py $out/bin/paperless-ngx  --prefix PYTHONPATH : "$PYTHONPATH"  --prefix PATH : "${path}" <ins> makeWrapper ${python.pkgs.celery}/bin/celery $out/bin/celery  --prefix PYTHONPATH : "$PYTHONPATH:$out/lib/paperless-ngx/src"  --prefix PATH : "${path}" </ins> ''; checkInputs = with python.pkgs.pythonPackages; [
Code change:
A clear and concise description of what the bug is. Prism Launcher doesn't allow enabling Feral GameMode or MangoHud under the "Performance" tab because it can't find it. Steps to reproduce the behavior: GameMode ( ) MangoHud ( ) Prism Launcher ( ) new instance in Prism Launcher instance and go to "Performance" tab A clear and concise description of what you expected to happen. GameMode and MangoHud should be able to be enabled when installed. 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.
Addressed here -

Related discussion:
text: , ghc_filesystem , msaClientID ? "" , jdks ? [ jdk17 jdk8 ] <ins> , gamemodeSupport ? true , gamemode </ins> }: let
Code change:
A clear and concise description of what the bug is. Prism Launcher doesn't allow enabling Feral GameMode or MangoHud under the "Performance" tab because it can't find it. Steps to reproduce the behavior: GameMode ( ) MangoHud ( ) Prism Launcher ( ) new instance in Prism Launcher instance and go to "Performance" tab A clear and concise description of what you expected to happen. GameMode and MangoHud should be able to be enabled when installed. 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.
Addressed here -

Related discussion:
text: quazip ghc_filesystem tomlplusplus <del> ] ++ lib.optional (lib.versionAtLeast qtbase.version "6") qtwayland; </del> <ins> ] ++ lib.optional (lib.versionAtLeast qtbase.version "6") qtwayland ++ lib.optional gamemodeSupport gamemode.dev; </ins> cmakeFlags = lib.optionals (msaClientID != "") [ "-DLauncher_MSA_CLIENT_ID=${msaClientID}" ] ++ lib.optionals (lib.versionAtLeast qtbase.version "6") [ "-DLauncher_QT_VERSION_MAJOR=6" ];
Code change:
A clear and concise description of what the bug is. Prism Launcher doesn't allow enabling Feral GameMode or MangoHud under the "Performance" tab because it can't find it. Steps to reproduce the behavior: GameMode ( ) MangoHud ( ) Prism Launcher ( ) new instance in Prism Launcher instance and go to "Performance" tab A clear and concise description of what you expected to happen. GameMode and MangoHud should be able to be enabled when installed. 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.
Addressed here -

Related discussion:
text: qtWrapperArgs = let libpath = with xorg; <del> lib.makeLibraryPath [ </del> <ins> lib.makeLibraryPath ([ </ins> libX11 libXext libXcursor
Code change:
A clear and concise description of what the bug is. Prism Launcher doesn't allow enabling Feral GameMode or MangoHud under the "Performance" tab because it can't find it. Steps to reproduce the behavior: GameMode ( ) MangoHud ( ) Prism Launcher ( ) new instance in Prism Launcher instance and go to "Performance" tab A clear and concise description of what you expected to happen. GameMode and MangoHud should be able to be enabled when installed. 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.
Addressed here -

Related discussion:
text: glfw openal stdenv.cc.cc.lib <del> ]; </del> <ins> ] ++ lib.optional gamemodeSupport gamemode.lib); </ins> in [ "--set LD_LIBRARY_PATH /run/opengl-driver/lib:${libpath}"
Code change:
does not running when you edit . Steps to reproduce the behavior: JSON value of Running service with my setting. ! Left is generated by nixos, Right is generated by supergfxd and edit me. ! I can run without and can edit conf generated by . However, I cannot run with same setting. (edit ) I use zephyrus G14. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
Please test
Complete ! Thank you !

Related discussion:
text: config = lib.mkIf cfg.enable { environment.systemPackages = [ pkgs.supergfxctl ]; <del> environment.etc."supergfxd.conf" = lib.mkIf (cfg.settings != null) { source = json.generate "supergfxd.conf" cfg.settings; }; </del> <ins> environment.etc."supergfxd.conf" = lib.mkIf (cfg.settings != null) { source = json.generate "supergfxd.conf" cfg.settings; mode = "0644"; }; </ins> services.dbus.enable = true;
Code change:
$ nixops --version Traceback (most recent call last): File "/nix/store/ni55r1wq3wp907bii23wzxnji0myd296-nixops-", line 5, in <modulefrom nixops import deployment File "/nix/store/ni55r1wq3wp907bii23wzxnji0myd296-nixops-1.4/lib/python2.7/site-", line 15, in <moduleimport nixops.statefile File "/nix/store/ni55r1wq3wp907bii23wzxnji0myd296-nixops-1.4/lib/python2.7/site-", line 6, in <moduleimport sqlite3 File "/nix/store/rawxj3af8l2sbxv6kpclwx5f1gdxi631-python-", line 24, in <modulefrom dbapi2 import File "/nix/store/rawxj3af8l2sbxv6kpclwx5f1gdxi631-python-", line 28, in <modulefrom sqlite3 import ImportError: No module named sqlite3 System: (NixOS: 16.09.1149. (Flounder)) Nix version: (1.11.4) Nixpkgs version: (16.09.1149.)
copy
Looks like it cannot find python C extensions for sqlite3. Looking at the nix expression for the package it should actually use pysqlite instead of sqlite from python stdlib.
It seems pysqlite is broken: But pythonPackage.sqlite3 is ok. If you replace the pysqlite dep by sqlite3 in nixops expression, nixops works again. Sorry, I don't really know why pysqlite is borken...
Fixed
Thanks!

Related discussion:
text: { stdenv, fetchurl, gmp }: stdenv.mkDerivation rec { <del> name = "ikarus-0.0.3"; </del> <ins> version = "0.0.3"; name = "ikarus-${version}"; </ins> src = fetchurl { <del> url = "http://ikarus-scheme.org/${name}.tar.gz"; </del> <ins> url = "http://launchpad.net/ikarus/0.0/${version}/+download/${name}.tar.gz"; </ins> sha256 = "0d4vqwqfnj39l0gar2di021kcf6bfpkc6g40yapkmxm6sxpdcvjv"; };