jiebi/CodeConvo huggingface dataset:
Change:
] ++ lib.optional (pythonOlder "3.5") typing; checkPhase = '' <del> ${cudaStubEnv}python test/run_test.py --exclude dataloader sparse torch utils </del> <ins> ${cudaStubEnv}python test/run_test.py --exclude dataloader sparse torch utils distributed </ins> ''; meta = {

Discussion:
I cannot build pytorch (cuda enabled or disabled), due to failing tests. I'm not sure why this is built locally instead of taken from the cache. I expect to get a shell where can be run and can be imported. Instead, I get an error: Full log is too long for pastebin, but the errors mostly look like: With these probably relevant lines near the beginning: Those two files both contain in my user shell.
I think it might be a sandboxing thing. Could you try running with ?
That doesn't help, I still get the same error with However, a sample nix that just does as its also fails: : Am I doing something wrong here?
Oops, I think you do need to be a "trusted user" to disable sandbox. You can try it by running: (or adding your user to nix.trustedUsers)
Yes, that works. Is there anything I can do to fix the package for other users? I could disable the problematic tests (I think they were enabled in ), or is there some way of saying a package must be built without sandboxing? Or only to run certain tests if sandboxing is disabled?
Yes, that works for pytorch but not for pytorchWithCuda: I tried using nixos-unstable and the PR but I got the same error. Any idea ?
I have in my - can you see if you see if it works for you then? If yes, I think there is some other package that needs with cuda enabled but it doesn't correctly depend on.
Tried with but same error. Tensorflow and tensorflowWithCuda work with my config.
Adding cudnn solved the problem. :champagne:
It is very odd that your initial command works for me without problems:
Indeed, I get lost in the different configurations that I tried. with works fine. Thanks.
Change:
cfg = config.services.nextcloud; fpm = config.services.phpfpm.pools.nextcloud; <del> phpPackage = let base = pkgs.php74; in base.buildEnv { extensions = { enabled, all }: with all; enabled ++ [ apcu redis memcached imagick ]; extraConfig = phpOptionsStr; }; </del> <ins> phpPackage = pkgs.php74.buildEnv { extensions = { enabled, all }: (with all; enabled ++ [ imagick ] # Always enabled # Optionally enabled depending on caching settings ++ optional cfg.caching.apcu apcu ++ optional cfg.caching.redis redis ++ optional cfg.caching.memcached memcached ) ++ cfg.phpExtraExtensions all; # Enabled by user extraConfig = toKeyValue phpOptions; }; </ins> toKeyValue = generators.toKeyValue { mkKeyValue = generators.mkKeyValueDefault {} " = ";

Discussion:
Many nextcloud extensions like need additional php extensions that are not part of the . It would be great to either: Provide an option to override the php package nextcloud uses, i.e. Or: Provide an option , and make the current extension selection its default value I'm opening this as an issue to get some feedback on what the better option is, and to get the naming right. CC maintainers
Meta: I'm not sure all labels I've applied make sense here. Feel free to remove inappropriate ones. Also: There is no PHP label?
cc
Change:
mkdir -p $out/bin for bin in Generator Imager ModelChecker PrologChecker Simulator Viewer; do <del> makeWrapper ${jre}/bin/java $out/bin/groove-''${bin,,}  </del> <ins> makeWrapper ${jre8}/bin/java $out/bin/groove-''${bin,,}  </ins> --add-flags "-jar $out/share/groove/bin/$bin.jar" done

Discussion:
Broken package: 'groove' Install package. Run 'groove-simulator'. File -New Grammar... Try to save, get an exception. system: host os: multi-user?: sandbox: version: channels(maestro): channels(root): nixpkgs: Permalink to broken package: It seems that the broken Nix package depends on OpenJDK17. Found that running their latest version (5.8.1) from SourceForge with the much older OpenJDK8 works just fine. Did not test with OpenJDK11. Probably just have to depend on an older Java version. Package version can also be bumped to 5.8.1. Don't have sufficient knowledge of Nix to fix this myself. Thanks
Probably should be assigned to
I think I've fixed it. I'll submit a PR soon. Also, I tested OpenJDK11 and it crashed there as well.
Change:
+ lib.optionalString isBootstrap "-boot" + lib.optionalString cursesUI "-cursesUI" + lib.optionalString qt5UI "-qt5UI"; <del> version = "3.25.1"; </del> <ins> version = "3.25.2"; </ins> src = fetchurl { url = "https://cmake.org/files/v${lib.versions.majorMinor version}/cmake-${version}.tar.gz"; <del> sha256 = "sha256-HFEdCVFq9JNpTtm68TxVlHo2OJZ01lei1eDM7caykdg="; </del> <ins> sha256 = "0g6k9sa23smh9z5dz8v6dqy89887gxc7s24gchpm7p9ip4ng49n0"; </ins> }; patches = [

Discussion:
Package name: cmake Latest released version: 3.25.2 <!-- Search your package here: --- Current version on the unstable channel: Current version on the stable/release channel: <!-- 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! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR.
Change:
, mesa , libxkbcommon , libxshmfence <del> , libglvnd </del> <ins> , libGL </ins> , alsa-lib , cairo , cups

Discussion:
/ is still present in the electron*-bin variants Would need a fix similar to vscode/spotify/... This only really affects users of EOL electron versions, since everything recent is using the source-built electron derivation by default on Linux (and I have no idea if/how Mac OS is affected by this issue, probably not). Steps to reproduce the behavior: run electron27-bin errors: CC the electron-bin maintainers_
This appears to be triggered by the libANGLE library: Specifically I believe the file needs to have its rpath patched so it can find the following libraries: One thing I noticed is that that doesn't show any search path before for these libraries. That leads me to believe that electron dynamically resolves the absolute path before calling , ignoring any environment variables or rpath changes in the process. We can fix this by either ensuring all the libraries included are properly patched, or perhaps replacing them with symlinks to nix-specific loaders like or . But I'm not sure if these libraries include additional functionality that chrome depends on.
Confirmed behavior with :
Note what wrote on the issues/PRs linked above:
Change:
discogs_client = discogs-client; # added 2021-07-02 djangorestframework-jwt = drf-jwt; # added 2021-07-20 django_environ = django-environ; # added 2021-12-25 <ins> django_extensions = django-extensions; # added 2022-01-09 </ins> django_redis = django-redis; # added 2021-10-11 django_taggit = django-taggit; # added 2021-10-11 dns = dnspython; # added 2017-12-10

Discussion:
python38Packages.djangoextensions and python39Packages.djangoextensions Fails to build. I discovered it as it was a dependency of Archivebox that also doesnt build now. Simple way to reproduce is: a file : I expected the package to build and not fail with errors. It appears it is the test's that fail and not the actual build. ! I have much larger file that I choose not to include as it is the same error i got in the minimal version and all the other clutter likely is not responsible. No maintainers for either of the packages :( Please run and paste the result. this path will be fetched (0.06 MiB download, 0.30 MiB unpacked):
Change:
<ins> { lib , stdenv , fetchFromGitHub , cmake , python3 }: stdenv.mkDerivation rec { pname = "box64"; version = "0.1.8"; src = fetchFromGitHub { owner = "ptitSeb"; repo = pname; rev = "v${version}"; hash = "sha256-6k8Enbafnj19ATtgmw8W7LxtRpM3Ousj1bpZbbtq8TM="; }; nativeBuildInputs = [ cmake python3 ]; cmakeFlags = [ "-DNOGIT=1" ] ++ ( if stdenv.hostPlatform.system == "aarch64-linux" then [ "-DARM_DYNAREC=ON" ] else [ "-DLD80BITS=1" "-DNOALIGN=1" ] ); installPhase = '' runHook preInstall install -Dm 0755 box64 "$out/bin/box64" runHook postInstall ''; doCheck = true; checkPhase = '' runHook preCheck ctest runHook postCheck ''; doInstallCheck = true; installCheckPhase = '' runHook preInstallCheck $out/bin/box64 -v runHook postInstallCheck ''; meta = with lib; { homepage = "https://box86.org/"; description = "Lets you run x86_64 Linux programs on non-x86_64 Linux systems"; license = licenses.mit; maintainers = with maintainers; [ gador ]; platforms = [ "x86_64-linux" "aarch64-linux" ]; }; } </ins>

Discussion:
Project description Box64 - Linux Userspace x86_64 Emulator with a twist, targeted at ARM64 Linux devices Can run 64-bit x86 binaries on ARM, like games. Metadata homepage URL: source URL: / license: mit platforms: linux
Change:
./services/web-apps/healthchecks.nix ./services/web-apps/hedgedoc.nix ./services/web-apps/hledger-web.nix <ins> ./services/web-apps/homebox.nix </ins> ./services/web-apps/honk.nix ./services/web-apps/icingaweb2/icingaweb2.nix ./services/web-apps/icingaweb2/module-monitoring.nix

Discussion:
Project description Like a simpler Snipe-IT for home usage. Keep track of inventories, warranties, and manuals. Metadata homepage URL: https://hay- source URL: license: APL3 platforms: presumably Go's platforms? Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
It makes use of , so is technically a blocker. I'm hoping it will work with to bypass that issue.
homebox was archived:
feel free to reopen if there's maintained, viable fork.
I see picking up activity, tentatively re-opening the issue for now. Will revisit to see if it keeps being maintained long term.
There's an active repo being worked on here:
Change:
, budgie-desktop-view , glib , gsettings-desktop-schemas <del> , magpie </del> <ins> , gnome </ins> , mate , nixos-artwork , nixos-background-light ? nixos-artwork.wallpapers.nineish

Discussion:
Budgie desktop stopped working a few months ago on because gsettings schema supplied by Budgie is missing settings which was recently to . This causes to crash during startup making Budgie DE setup unusable. budgie-desktop from . .
Are you using Budgie alongside another desktop? Otherwise LightDM is the preferred choice for Budgie, but I will still look into this.
Oh, I didn't know that. When I switched from gnome to budgie, I kept and everything worked, so I kept it. I can confirm that if I use , everything works.
Change:
./no-etc-install.patch ./fix-qemu-ga.patch ./9p-ignore-noatime.patch <ins> (fetchpatch { url = "https://git.qemu.org/?p=qemu.git;a=patch;h=d52680fc932efb8a2f334cc6993e705ed1e31e99"; name = "CVE-2019-12155.patch"; sha256 = "0h2q71mcz3gvlrbfkqcgla74jdg73hvzcrwr4max2ckpxx8x9207"; }) </ins> ] ++ optional nixosTestRunner ./force-uid0-on-9p.patch ++ optionals stdenv.hostPlatform.isMusl [ (fetchpatch {

Discussion:
, (nixos-unstable) Scanned versions: nixos-unstable: . May contain false positives.
Change:
genericNetwork = override: let gateway = optional (cfg.defaultGateway != null && (cfg.defaultGateway.address or "") != "") cfg.defaultGateway.address ++ optional (cfg.defaultGateway6 != null && (cfg.defaultGateway6.address or "") != "") cfg.defaultGateway6.address; <del> in optionalAttrs (gateway != [ ]) { routes = override [ { </del> <ins> makeGateway = gateway: { </ins> routeConfig = { Gateway = gateway; GatewayOnLink = false; }; <del> } ]; </del> <ins> }; in optionalAttrs (gateway != [ ]) { routes = override (map makeGateway gateway); </ins> } // optionalAttrs (domains != [ ]) { domains = override domains; };

Discussion:
Setting the default IPV4 and IPV6 gateway using and respectively results in a system configuration in which only the IPV6 default gateway is configured. Looking at the generated network configuration files, this seems to be due to an order of precedence and non-merging behaviour within the section of the config. My system has only one network interface with both an ipv4 and ipv6 address configured. I expect both routes to be applied to this interface. Reverse-engineering the , I discovered that the gateways are configured differently to what would apply. As a result, I was able to test the alternative method and found that the following would correctly configure the network: With that, I also noticed that the entries were to the section rather than the section. This would imply to me that the handling of defaultGateway should do the same. both and with . the configuration. to view the active routes, and note the lack of an IPV4 default route. Both IPV4 and IPV6 default routes/gateways should be configured. The behaviour should match setting to the value of each gateway. Broken configuration example: Working configuration example:
looks like we should be generating one route per gateway instean of one route with multiple gateways. putting the gateways into would have the same effect, but emitting multiple routes seems clearer.
Change:
openssl_1_1 = common { version = "1.1.1a"; sha256 = "0hcz7znzznbibpy3iyyhvlqrq44y88plxwdj32wjzgbwic7i687w"; <del> patches = [ ./1.1/nix-ssl-cert-file.patch ]; </del> <ins> patches = [ ./1.1/nix-ssl-cert-file.patch (if stdenv.hostPlatform.isDarwin then ./1.1/use-etc-ssl-certs-darwin.patch else ./1.1/use-etc-ssl-certs.patch) ]; </ins> withDocs = true; };

Discussion:
We don't seem to have a sane default in openssl 1.1. Example: Compare to openssl 1.0.2 (default ATM): The problem also propagates to (and probably elsewhere). Of course, the CA path can be overridden via parameters and/or env vars, but we do need a sane default, too. With 1.0.2 we apply to get default, whereas with 1.1 I can't see any similar change. I haven't dug deep so far. I guess you won't remember why you "dropped" the patch in ? EDIT: I see the patched file has moved in upstream source tree.
Change:
''; }); <del> caddy = callPackage ../servers/caddy { }; xcaddy = callPackage ../servers/caddy/xcaddy { }; </del> traefik = callPackage ../servers/traefik { }; traefik-certs-dumper = callPackage ../tools/misc/traefik-certs-dumper { };

Discussion:
Caddy fails to build for riscv64 Steps to reproduce the behavior: ... ... ... 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. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
(please fill out more parts of the bug report template next time) Assuming this is , likely an instance of . Pinging maintainers:
Hi, thanks for the ping :) The fix for this is fairly trivial. Either skip the shell completions/man pages[^1], or use something like But I am upset that you ( didn't even care enough to do the bare minimum and fill out the issue template. [^1]: Technically only the kills the build, not the , because bash pipefail defaults.
i'm sorry for the issue template, it was more of a quick note to myself. i'll do it right next time
Change:
<del> { lib, stdenv, fetchFromGitHub, makeWrapper, runCommand </del> <ins> { lib, stdenv, fetchFromGitHub, buildGoModule, makeWrapper, runCommand </ins> , cacert, moreutils, jq, git, pkg-config, yarn, python3 , esbuild, nodejs-16_x-openssl_1_1, libsecret, xorg, ripgrep , AppKit, Cocoa, Security, cctools }:

Discussion:
Steps to reproduce the behavior: or see: Can someone nail the problem down to a specific pr or commit? <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
Broken because of PR
Now broken because is insecure.
waiting for as nodejs 18 migration is blocked
Change:
freshrss-sqlite = handleTest ./freshrss-sqlite.nix {}; freshrss-pgsql = handleTest ./freshrss-pgsql.nix {}; freshrss-http-auth = handleTest ./freshrss-http-auth.nix {}; <ins> freshrss-none-auth = handleTest ./freshrss-none-auth.nix {}; </ins> frigate = handleTest ./frigate.nix {}; frp = handleTest ./frp.nix {}; frr = handleTest ./frr.nix {};

Discussion:
Unable to use freshrss. It returns the error . Try http://localhost, be redirected to http://localhost/i/?rid=, see the error It should run without errors. thank you all for maintaining this module Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I think this issue is happening because the default user isn't being created by the 'freshrss-config' service when authType none is specified. I'll work on a PR to fix this shortly. In the meanwhile, I think a workaround would be to start freshrss with authType form configured once, to initialize the default user, then switching to authType none afterwards.
Change:
sed -i 's,(option(WITH_SHARED_LIBUV.*)OFF,1ON,' CMakeLists.txt rm -rf deps/libuv ''; <del> propagatedBuildInputs = [ pkgs.libuv ]; </del> <ins> buildInputs = [ pkgs.libuv ]; </ins> passthru = { <del> libluv = self.luv.override({ </del> <ins> libluv = self.luv.override ({ </ins> preBuild = self.luv.preBuild + '' <del> sed -i 's,(option(BUILD_MODULE.*)ON,1OFF,' CMakeLists.txt sed -i 's,(option(BUILD_SHARED_LIBS.*)OFF,1ON,' CMakeLists.txt sed -i 's,${"${INSTALL_INC_DIR}"},${placeholder "out"}/include/luv,' CMakeLists.txt </del> <ins> sed -i 's,(option(BUILD_MODULE.*)ON,1OFF,' CMakeLists.txt sed -i 's,(option(BUILD_SHARED_LIBS.*)OFF,1ON,' CMakeLists.txt sed -i 's,${"${INSTALL_INC_DIR}"},${placeholder "out"}/include/luv,' CMakeLists.txt </ins> ''; <ins> nativeBuildInputs = [ pkgs.fixDarwinDylibNames ]; # Fixup linking libluv.dylib, for some reason it's not linked against lua correctly. NIX_LDFLAGS = pkgs.lib.optionalString pkgs.stdenv.isDarwin (if isLuaJIT then "-lluajit-${lua.luaversion}" else "-llua"); </ins> }); }; });

Discussion:
Describe the bug In PR , was as a build input for Neovim. This PR is now live on the channel. On macOS 10.14.6 Neovim now fails to build for me. As best I can tell this is because is failing to build. I'm not certain whether getting building on Darwin will lead to Neovim building successfully on Darwin, but it seems like it's at least a necessary step. ( might also be relevant here.) To Reproduce Steps to reproduce the behavior: Expected behavior builds successfully. Additional context <details<summaryOutput of :</summary<p</p</detailsMetadata Maintainer information:
CCing some relevant folks,
CC
Change:
in overrideCC targetStdenv cc; <del> useMoldLinker = stdenv: let bintools = stdenv.cc.bintools.override { extraBuildCommands = '' wrap ${stdenv.cc.bintools.targetPrefix}ld.mold ${../build-support/bintools-wrapper/ld-wrapper.sh} ${pkgs.mold}/bin/ld.mold wrap ${stdenv.cc.bintools.targetPrefix}ld ${../build-support/bintools-wrapper/ld-wrapper.sh} ${pkgs.mold}/bin/ld.mold ''; }; in stdenv.override (old: { allowedRequisites = null; cc = stdenv.cc.override { inherit bintools; }; # gcc >12.1.0 supports '-fuse-ld=mold' # the wrap ld above in bintools supports gcc <12.1.0 and shouldn't harm >12.1.0 # https://github.com/rui314/mold#how-to-use } // lib.optionalAttrs (stdenv.cc.isClang || (stdenv.cc.isGNU && lib.versionAtLeast stdenv.cc.version "12")) { mkDerivationFromStdenv = extendMkDerivationArgs old (args: { NIX_CFLAGS_LINK = toString (args.NIX_CFLAGS_LINK or "") + " -fuse-ld=mold"; }); }); </del> <ins> useMoldLinker = stdenv: if stdenv.targetPlatform.isDarwin then throw "Mold can't be used to emit Mach-O (Darwin) binaries" else let bintools = stdenv.cc.bintools.override { extraBuildCommands = '' wrap ${stdenv.cc.bintools.targetPrefix}ld.mold ${../build-support/bintools-wrapper/ld-wrapper.sh} ${pkgs.mold}/bin/ld.mold wrap ${stdenv.cc.bintools.targetPrefix}ld ${../build-support/bintools-wrapper/ld-wrapper.sh} ${pkgs.mold}/bin/ld.mold ''; }; in stdenv.override (old: { allowedRequisites = null; cc = stdenv.cc.override { inherit bintools; }; # gcc >12.1.0 supports '-fuse-ld=mold' # the wrap ld above in bintools supports gcc <12.1.0 and shouldn't harm >12.1.0 # https://github.com/rui314/mold#how-to-use } // lib.optionalAttrs (stdenv.cc.isClang || (stdenv.cc.isGNU && lib.versionAtLeast stdenv.cc.version "12")) { mkDerivationFromStdenv = extendMkDerivationArgs old (args: { NIX_CFLAGS_LINK = toString (args.NIX_CFLAGS_LINK or "") + " -fuse-ld=mold"; }); }); </ins> /* Modify a stdenv so that it builds binaries optimized specifically for the machine they are built on.

Discussion:
is broken on macOS. Steps to reproduce the behavior: shell with as linker () in in macOS. : to compile any program (e.g. ): In one line: Program links and compiles. There are multiple issues: on Darwin requires absolute path for linker, while doesn't add path. This is not the issue on Linux, for some reason. with absolute path, it doesn't work when targeting Darwin, since macOS support is somewhat incomplete. There is an abandoned ex-commercial fork of that supports macOS: . [author of ] [maintainers of ] <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Looks like mold has . I guess we can just throw if is Darwin-based. I can make a PR a bit later. I also don't think that pulling to Nixpkgs would be a good idea, since it's not maintained properly anymore.
Change:
services.rpcbind.enable = true; <ins> services.nfs.idmapd.settings = { General = mkMerge [ { Pipefs-Directory = rpcMountpoint; } (mkIf (config.networking.domain != null) { Domain = config.networking.domain; }) ]; Mapping = { Nobody-User = "nobody"; Nobody-Group = "nogroup"; }; Translation = { Method = "nsswitch"; }; }; </ins> system.fsPackages = [ pkgs.nfs-utils ]; boot.initrd.kernelModules = mkIf inInitrd [ "nfs" ];

Discussion:
If you want root access to an NFS share secured with Kerberos, you need to modify the default . Currently, I override the source, because NixOS has no options to modify : The text is mostly copied from the default NixOS . The only changes are This solution is brittle, and requires manual intervention if the default ever changes. I'm not sure exactly what the NixOS options should look like, but there should be mechanisms to modify in NixOS. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
what about an option like so you can easily override/append values as you see fit?
That looks great. I'm a big fan of RFC 42 :) Just one question though. Can you remove an option, such as ?
Good question. can we bug you for some advice on how you can remove values from a option?
There's nothing builtin for that. The best that can be done is to just filter out values during string generation. Though in INI's case, is also a valid value in INI files, so that might not be a great idea. There is that adds a way to "unset" values, though I haven't looked into it much.
Thanks for mentioning without the ability to remove values would this not work?
I did a double-check on , and it looks like and are actually separate, but related. defaults to the value of . Also, the default value of is already , so removing it in my configuration had no effect. On that note, we may consider removing , as that is already the default. Regardless, your RFC 42 solution should work, even without the ability to remove values.
are you interested in opening a PR? Feel free to use the branch I posted.
I can open a pull request. Just one question: is there a reason the option and variables are called instead of ?
Typo
pull request is up. I fixed the typo and a syntax error.