jiebi/CodeConvo huggingface dataset:
Change:
# Tell the Nix evaluator to garbage collect more aggressively. # This is desirable in memory-constrained environments that don't # (yet) have swap set up. <del> environment.variables.GC_INITIAL_HEAP_SIZE = "100000"; </del> <ins> environment.variables.GC_INITIAL_HEAP_SIZE = "1M"; </ins> # Make the installer more likely to succeed in low memory # environments.  The kernel's overcommit heustistics bite us

Discussion:
I got the warning multiple times when installing NixOS from . [root nix-shell -p nix-info --run "nix-info -m" GC Warning: Bad initial heap size - ignoring it. GC Warning: Bad initial heap size - ignoring it. system: host os: multi-user?: sandbox: GC Warning: Bad initial heap size - ignoring it. version: GC Warning: Bad initial heap size - ignoring it. channels(root): GC Warning: Bad initial heap size - ignoring it. nixpkgs:
Out of curiosity -- what's the hardware you've seen this on? Unless it's a recent regression that happens even on smaller boxes, I first saw this when installing 18.09 on a machine with a somewhat ridiculously large amount of RAM.
I get the same warning running on a Rasberry Pi 3 (aarch64). Warning is coming from () and seems to be caused by this option:
I got the same warning when installing 18.09 on a Thinkpad T570 with 16GB ram. and as correctly stated seems to be caused by
Seen this just now on a test VM with no storage, just running a 18.09-minimal live CD. The VM has 1 vCPU and 1GB vRAM.
Solved in
Change:
inherit (pkgs) libusb1; }; <ins> pyuseragents = callPackage ../development/python-modules/pyuseragents { }; </ins> pyutilib = callPackage ../development/python-modules/pyutilib { }; pyuv = callPackage ../development/python-modules/pyuv { };

Discussion:
Project description Translate, transliterate, get the language of texts in no time with the help of multiple APIs! Metadata homepage URL: source URL: license: agpl3 platforms: linux  It (most likely) runs on many platforms, but I am specifically interested in linux support.
Sweet! Thanks.
Change:
wtforms = super.wtforms.overridePythonAttrs (oldAttrs: rec { version = "2.3.1"; <del> src = oldAttrs.src.override { </del> <ins> src = fetchPypi { pname = "WTForms"; </ins> inherit version; sha256 = "sha256-hhoTs65SHWcA2sOydxlwvTVKY7pwQ+zDqCtSiFlqGXI="; };

Discussion:
Steps to reproduce the behavior: archivy Add any other context about the problem here. nixos 24.05, nixos-unstable at Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
appimageTools.wrapType2 rec { inherit pname version src; <del> extraPkgs = pkgs: [ pkgs.texliveMedium pkgs.pandoc ]; </del> <ins> extraPkgs = pkgs: [ pkgs.texliveMedium pkgs.pandoc ]; </ins> extraInstallCommands = '' <ins> source "${makeWrapper}/nix-support/setup-hook" wrapProgram $out/bin/zettlr  --add-flags "''${NIXOS_OZONE_WL:+''${WAYLAND_DISPLAY:+--ozone-platform-hint=auto --enable-features=WaylandWindowDecorations}}" </ins> install -m 444 -D ${appimageContents}/Zettlr.desktop $out/share/applications/Zettlr.desktop install -m 444 -D ${appimageContents}/Zettlr.png $out/share/icons/hicolor/512x512/apps/Zettlr.png substituteInPlace $out/share/applications/Zettlr.desktop  <del> --replace 'Exec=AppRun' 'Exec=${pname}' </del> <ins> --replace-fail 'Exec=AppRun' 'Exec=${pname}' </ins> ''; <del> meta = with lib; { </del> <ins> meta = { </ins> description = "Markdown editor for writing academic texts and taking notes"; homepage = "https://www.zettlr.com"; platforms = [ "x86_64-linux" ]; <del> license = licenses.gpl3; maintainers = with maintainers; [ tfmoraes ]; </del> <ins> license = lib.licenses.gpl3; maintainers = with lib.maintainers; [ tfmoraes ]; </ins> mainProgram = "zettlr"; }; }

Discussion:
Since Zettlr is an Electron app, it needs to be run with certain command-line arguments on Wayland (specifically ). In NixOS, setting the environment variable to should automatically tell packages to use this command-line argument, but this requires integrating it into the package file (see ) for an example. The Zettlr package does not currently do this, which results in pixelated and glitchy graphics on Wayland unless it is manually run with the correct command-line arguments. This should be a pretty simple fix, as it has been implemented before for many other Electron apps by creating a binary wrapper.
Change:
<ins> { stdenv , runCommand , makeBinaryWrapper , binutils , expectedArch ? stdenv.hostPlatform.parsed.cpu.name }: runCommand "make-binary-wrapper-test-cross" { nativeBuildInputs = [ makeBinaryWrapper binutils ]; inherit expectedArch; } '' touch prog chmod +x prog makeWrapper prog $out read -r _ arch < <($READELF --file-header $out | grep Machine:) if [[ ''${arch,,} != *"''${expectedArch,,}"* ]]; then echo "expected $expectedArch, got $arch" exit 1 fi '' </ins>

Discussion:
making a pr fixing cross compilation for some things and found this
... and defaults to which is per shrug : /
Something that seems to fix the problem, weirdly, is to add to instead of , and use in I have no idea what's going on, need a cross-compilation guru ( ?).
is special: All packages in a package set are host→target (e.g. the normal attribute), however is derived from and re-exposed as the thing that builds this package set. This gives rise to the inconsistency that is one of the few attributes in the package set that's build→host. Putting into (where it conceptually belongs) will of course pick , since it itself comes from . To pick the default compiler we should use to build here, it should take by default where would then be the package set produced by which is the actual cross compiled set: . We need to jump through these hoops because, unfortunately the default compiler / libc etc. picking logic is only done as part of picking the 's from the previous package set.
Do you mean host→target here?
Yes, fixed.
Attempting a fix in
Thanks for reporting this Artturin! Verified the PR that was made and merged :)
Change:
{ lib, stdenv, fetchFromGitHub, cmake, gettext, msgpack, libtermkey, libiconv <ins> , fetchpatch </ins> , libuv, lua, ncurses, pkg-config , unibilium, gperf , libvterm-neovim

Discussion:
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:
Change:
<ins> diff --git a/Cargo.lock b/Cargo.lock index 5ae2bd6..e4c6f18 100644 --- a/Cargo.lock +++ b/Cargo.lock @@ -5676,9 +5676,9 @@ dependencies = [ [[package]] name = "time" -version = "0.3.34" +version = "0.3.36" source = "registry+https://github.com/rust-lang/crates.io-index" -checksum = "c8248b6521bb14bc45b4067159b9b6ad792e2d6d754d6c41fb50e29fefe38749" +checksum = "5dfd88e563464686c916c7e46e623e520ddc6d79fa6641390f2e3fa86e83e885" dependencies = [ "deranged", "itoa", @@ -5699,9 +5699,9 @@ checksum = "ef927ca75afb808a4d64dd374f00a2adf8d0fcff8e7b184af886c3c87ec4a3f3" [[package]] name = "time-macros" -version = "0.2.17" +version = "0.2.18" source = "registry+https://github.com/rust-lang/crates.io-index" -checksum = "7ba3a3ef41e6672a2f0f001392bb5dcd3ff0a9992d618ca761a11c3121547774" +checksum = "3f252a68540fde3a3877aeea552b832b40ab9a69e318efd078774a01ddee1ccf" dependencies = [ "num-conv", "time-core", </ins>

Discussion:
The czkawka package is missing ffmpeg as a dependency. If ffmpeg is not found you get this error when trying to compare video files: Ignore the snap part, it throws this error when it can't find ffmpeg, regardless if snap or not. 't have ffmpeg installed on you system. comparing videos in czkawka throws error ffmpeg error. Just works. No error. Just works. First issue I've reported here, hopefully I'm doing this right. <!-- 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]:
Before I propose any changes, let me know a thing or two. When you install both ffmpeg and czkawka, then czkawka finds ffmpeg, correct?
Correct. It finds it no problem.
Change:
- [Localsend](https://localsend.org/), an open source cross-platform alternative to AirDrop. Available as [programs.localsend](#opt-programs.localsend.enable). <ins> - [cryptpad](https://cryptpad.org/), a privacy-oriented collaborative platform (docs/drive/etc), has been added back. Available as [services.cryptpad](#opt-services.cryptpad.enable). </ins> - [realm](https://github.com/zhboner/realm), a simple, high performance relay server written in rust. Available as [services.realm.enable](#opt-services.realm.enable). - [Playerctld](https://github.com/altdesktop/playerctl), a daemon to track media player activity. Available as [services.playerctld](option.html#opt-services.playerctld).

Discussion:
Project description CryptPad is a collaborative office suite that is end-to-end encrypted and open-source. Enable this a service for NixOS. Metadata homepage URL: source URL: license: agpl2 platforms: unix, linux, darwin, ...
CryptPad used to be included in nixpkgs, but it was removed because there weren't enough maintainers. The removal occurred with the commits and .
Not quite true: it was removed because they had a strong dependency on out-of-date software. . Now, there is an ongoing effort to re-introduce it in : .
Change:
, buildPythonPackage , defusedxml , fetchPypi <ins> , fetchpatch </ins> , ipywidgets , jinja2 , jupyterlab-pygments

Discussion:
Build of failed on x86_64-linux as of . This is currently breaking . maintainers cc: python310Packages.nbconvert maintainers cc: Other cc: n/a nixpkgs at commit This issue was automatically generated by . that created this issue. Internal tags: -
Looks like this is due to was updated from 0.8.4 to 2.0.4, which doesn't satisfy 's requirement of .
Ah, seems it's going to be solved by .
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
inherit lib; }; <ins> mkNongnuDevelPackages = { pkgs, lib }: import ../applications/editors/emacs/elisp-packages/nongnu-devel-packages.nix { inherit (pkgs) buildPackages; inherit lib; }; </ins> mkNongnuPackages = { pkgs, lib }: import ../applications/editors/emacs/elisp-packages/nongnu-packages.nix { inherit (pkgs) buildPackages; inherit lib;

Discussion:
Project description NonGNU-devel ELPA Packages; i.e., development versions of the already packaged Metadata homepage URL: source URL: license: probably (guessed by looking at ) platforms: probably all (guessed by looking at ) Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
This feels like something that should only live in the emacs-overlay, not in Nixpkgs.
Consider that the other two supported ELPAs have both their stable/unstable versions supported in nixpkgs: elpa/elpaDevel; melpaStable/melpa (see to quickly fact-check). What's the reason for this feeling; why should nongnu be an exception?
I think the same about the others.
Change:
xwayland.enable = mkEnableOption ("XWayland") // { default = true; }; <del> envVars.enable = mkEnableOption null // { default = true; example = false; description = '' Set environment variables for Hyprland to work properly. Enabled by default. ''; }; </del> systemd.setPath.enable = mkEnableOption null // { default = true; example = false;

Discussion:
A clear and concise description of what the bug is. In , XDGSESSIONTYPE is now set to wayland by default for Hyprland users. However, SDDM will crash when this env var is set. Steps to reproduce the behavior: SDDM with Set under . SDDM greet will never show, and the screen will be black. These two lines can be seen in journalctl, and they are not present for boots from older generations. SDDM does not crash. <!-- 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]:
Did you enable wayland support for SDDM? ()
Thanks, enabling that option fixed the issue! Would be nice if there is an config assertion for this.
Haven't checked the implications but maybe sddm should just enable by default?
enabling wayland for SDDM, makes it impossible for me to start X11 only sessions (eg Pantheon) Is this expected, or is there a way to use SDDM with wayland and X11 sessions?
Same issue here, workaround mentioned in worked for me. I found the following stacktrace in the logs, not sure if/ how this might be helpful.
The proper workaround for now would be to set . Those are envvars that should be set only when the hyprland session starts, not categorically set.
Thanks, this worked for me. I can now start X11 sessions again :)
Same problem here using Hyprland with Budgie as a second desktop. Thanks for solution :+1: works!
Change:
# # The following selects the correct Clang version, matching the version # used in Swift, and applies the same libc overrides as `apple_sdk.stdenv`. <del> clang = if pkgs.stdenv.isDarwin </del> <ins> clang = let # https://github.com/NixOS/nixpkgs/issues/295322 clangNoMarch = swiftLlvmPackages.clang.override { disableMarch = true; }; in if pkgs.stdenv.isDarwin </ins> then <del> swiftLlvmPackages.clang.override rec { </del> <ins> clangNoMarch.override rec { </ins> libc = apple_sdk.Libsystem; bintools = pkgs.bintools.override { inherit libc; }; # Ensure that Swift’s internal clang uses the same libc++ and libc++abi as the

Discussion:
Since was merged into the master, swift cannot be built on aarch64. Steps to reproduce the behavior: reported in I'm not familiar with swift or clang, but I'm using the following overlay as a workaround until it's fixed. <!-- 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]:
states that this only fixed the swift build but all downstream packages are still broken. re-opening.
Actually, it seems only dark-mode-notify is broken, others seem fine. Probably because it uses Cocoa or disables sandbox. I don't know for sure.
I noticed that my personal package does not build either. Maybe it's because of swift itself or swiftpm?
The above open PR seems to run into the same issue…
Change:
in { php72 = generic { <del> version = "7.2.29"; sha256 = "08xry2fgqgg8s0ym1hh11wkbr36av3zq1bn4krbciw1b7x8gb8ga"; </del> <ins> version = "7.2.31"; sha256 = "0057x1s43f9jidmrl8daka6wpxclxc1b1pm5cjbz616p8nbmb9qv"; </ins> # https://bugs.php.net/bug.php?id=76826 extraPatches = optional stdenv.isDarwin ./php72-darwin-isfinite.patch; }; php73 = generic { <del> version = "7.3.16"; sha256 = "0bh499v9dfgh9k51w4rird1slb9rh9whp5h37fb84c98d992s1xq"; </del> <ins> version = "7.3.19"; sha256 = "199l1lr7ima92icic7b1bqlb036md78m305lc3v6zd4zw8qix70d"; </ins> # https://bugs.php.net/bug.php?id=76826 extraPatches = optional stdenv.isDarwin ./php73-darwin-isfinite.patch; }; php74 = generic { <del> version = "7.4.6"; sha256 = "0j133pfwa823d4jhx2hkrrzjl4hswvz00b1z58r5c82xd5sr9vd6"; </del> <ins> version = "7.4.7"; sha256 = "0ynq4fz54jpzh9nxvbgn3vrdad2clbac0989ai0yrj2ryc0hs3l0"; </ins> }; }

Discussion:
, CVSSv3=7.5 (nixos-20.03) CVSSv3=7.5 (nixos-20.03) CVSSv3=5.3 (nixos-20.03) Scanned versions: nixos-20.03: . May contain false positives. Cc Cc
CVE-2018-: imap_mail fixed in 7.2.14 and 7.3.0
CVE-2020-7067: EBCDIC decode fixed in 7.2.30, 7.3.17 and 7.4.5
CVE-2019-: fixed in 7.2.30, 7.3.17, 7.4.5
merged - closeme

, CVSSv3=8.8 (nixos-20.03) CVSSv3=5.4 (nixos-20.03) Scanned versions: nixos-20.03: . May contain false positives. Cc Cc
See also: ,
CVE-2020-7065 fixed in 7.4.4 and 7.3.16
merged - closing

, CVSSv3=5.3 (nixos-20.03) Scanned versions: nixos-20.03: . May contain false positives. Cc Cc
See also:
Fixed in 7.4.6, 7.3.18, and 7.2.31
merged - closing

, CVSSv3=6.1 (nixos-unstable) Scanned versions: nixos-unstable: . May contain false positives.
This vulnerability is not present in the CPEs. Closing as a FP.

, CVSSv3=7.5 (nixos-20.03) Scanned versions: nixos-20.03: . May contain false positives.
merged - closing

, CVSSv3=8.8 (nixos-19.09) CVSSv3=7.5 (nixos-19.09) CVSSv3=5.4 (nixos-19.09) CVSSv3=4.3 (nixos-19.09) Scanned versions: nixos-19.09: . May contain false positives.
won't backport
Change:
let cfg = config.services.keyd; settingsFormat = pkgs.formats.ini { }; <del> in { options = { services.keyd = { enable = mkEnableOption (lib.mdDoc "keyd, a key remapping daemon"); </del> <ins> keyboardOptions = { ... }: { options = { </ins> ids = mkOption { type = types.listOf types.string; default = [ "*" ];

Discussion:
Currently options of keyd service () allow for creating single configuration file (). I need to apply different configs to different keyboards (which is possible by creating multiple conf files in ). Could NixOS keyd module expose suitable option(s) for this?
I'll look into it. Can you provide an example of what these files should look like? Is it the same as "" but with a different "id" section?
Thanks very much! Exactly. The format of all conf files is the same. Each file specifies different to match different keyboards.
Ok, I will think how I can do it nicely soon
this patch is ready. If you are using unstable nixos, you can update the packages with with a flake switch (do you use flakes?). Can you confirm that the multi-file configuration is working now?
Hello, I am using keyd and NixOS unstable. I updated my to account for the changes related to this issue. I then ran and my built-in laptop keyboard, which I use keyd with, stopped responding to input. I plugged in an external keyboard, which worked fine, and had a look at the systemd logs for keyd.service and the new configuration files. I did not see anything unusual. I then ran and my keyboard started working again. I can consistently reproduce this by rebooting and re-running the above command. If anyone else has this issue and doesn't have an external keyboard handy, I suggest trying the following steps, as these also allowed me to update without disabling my keyboard: out the portion of your NixOS config. NixOS update command e.g. portion and run again As for the new configuration: I have not tested the multi-file configuration properly as I only use it for my laptop keyboard but the new file layout looks correct .
Hi unfortunately I also have this problem from time to time when the home manager restarts many services at once. I have an easier workaround - just press . The keyd docs say this command will stop keyd, but for me it restarts it and everything works like a charm. Also try using or instead of and you should probably run into this situation less often. I think because when you create a lock file from scratch, all services will be restarted, but with the only some of them. I'm not sure though, just a guess.
Change:
# `native-image -H:CLibraryPath=''${lib.getLib graalvmXX-ce}/lib ...` and reduce # closure size by not depending on GraalVM $out (that is much bigger) # we always use glibc here, since musl is only supported for static compilation <del> mkdir -p "$lib/lib" </del> for f in "${glibc}/lib/"*; do ln -s "$f" "$lib/lib/$(basename $f)" done

Discussion:
On current nixpkgs unstable, GraalVM 11 won't build (also breaking clojure-lsp, clj-kondo, babashka, etc). Steps to reproduce the behavior: macOS: It should build successfully graalvm17-ce fails for the same reason. GraalVM package maintainers: Please run and paste the result.
My bad, this was probably one change that I made on the previous refactor. This PR should fix it:
Change:
buildInputs = [ libpng ]; configureFlags = [ <del> "--with-rgbtxt=${netpbm}/share/netpbm/misc/rgb.txt" </del> <ins> "--with-rgbtxt=${netpbm.out}/share/netpbm/misc/rgb.txt" </ins> ]; meta = with stdenv.lib; {

Discussion:
no $ Add to installPhase
For some reason netpbm is installing the symlink to . Will be fixed by

Describe the bug Netpbm misses TIFF converters, such as . To Reproduce Steps to reproduce the behavior: to find some commands. Expected behavior TIFF converters installed with Netpbm. Additional context libtiff is required to build the following Netpbm programs: , , and (). Indeed is input for the , but TIFF converters are missed. Metadata output:
Change:
bazelTarget = "//ibazel"; fetchAttrs = { <ins> inherit patches; </ins> preBuild = '' patchShebangs . <del> # tell rules_go to use the Go binary found in the PATH sed -e 's:go_register_toolchains():go_register_toolchains(go_version = "host"):g' -i WORKSPACE </del> ''; preInstall = ''

Discussion:
I can't build bazel-watcher on the latest master <details<summaryShell session</summary</detailsPlease run and paste the results. system: host os: multi-user?: sandbox: version: channels(root): channels(kalbasit): channels(yl): nixpkgs: cc
Change:
<ins> # This test runs a container through gvisor and checks if simple container starts import ./make-test-python.nix ({ pkgs, ...} : { name = "gvisor"; meta = with pkgs.stdenv.lib.maintainers; { maintainers = [ andrew-d ]; }; nodes = { gvisor = { pkgs, ... }: { virtualisation.docker = { enable = true; extraOptions = "--add-runtime runsc=${pkgs.gvisor}/bin/runsc"; }; networking = { dhcpcd.enable = false; defaultGateway = "192.168.1.1"; interfaces.eth1.ipv4.addresses = pkgs.lib.mkOverride 0 [ { address = "192.168.1.2"; prefixLength = 24; } ]; }; }; }; testScript = '' start_all() gvisor.wait_for_unit("network.target") gvisor.wait_for_unit("sockets.target") # Start by verifying that gvisor itself works output = gvisor.succeed( "${pkgs.gvisor}/bin/runsc -alsologtostderr do ${pkgs.coreutils}/bin/echo hello world" ) assert output.strip() == "hello world" # Also test the Docker runtime gvisor.succeed("tar cv --files-from /dev/null | docker import - scratchimg") gvisor.succeed( "docker run -d --name=sleeping --runtime=runsc -v /nix/store:/nix/store -v /run/current-system/sw/bin:/bin scratchimg /bin/sleep 10" ) gvisor.succeed("docker ps | grep sleeping") gvisor.succeed("docker stop sleeping") ''; }) </ins>

Discussion:
"Sandboxed container runtime" Bonus points for NixOS option for docker support :P. But just having it to poke at would be neat, i think!
I've looked quickly at this, and it seems like the main limitation in implementing this is . I think we either have to patch Bazel in NixOS or any Bazel package that compiles Go to fix this...
Change:
''} # Load X defaults. <del> if test -e ~/.Xdefaults; then </del> <ins> if test -e ~/.Xresources; then ${xorg.xrdb}/bin/xrdb -merge ~/.Xresources elif test -e ~/.Xdefaults; then </ins> ${xorg.xrdb}/bin/xrdb -merge ~/.Xdefaults fi

Discussion:
nixos/modules/services/x11/display- has code to load ~/.Xdefaults, but not ~/.Xresources, even though ~/.Xdefaults is the deprecated version of ~/.Xresources