jiebi/CodeConvo huggingface dataset:
Change:
A clear and concise description of what the bug is. Matrix server dendrite does not start after upgrade to 0.13.1 This is fixed in - Prepare statement on an existing transaction Steps to reproduce the behavior: dendrite < 0.13.1 running as a service with sqlite as database backend which upgrades dendrite to 0.13.1 as per Matrix server dendrite not crashing fixed in Please run and paste the result.
Sorry for that, it seems like the issue slipped through the test suite, because it starts up an empty dendrite instance. I'll make a PR to apply the commit provided above.
I've proposed PR to address this issue. Let me know if the issue still occurs after applying the commit.
Works :partying_face: thanks a lot for the quick fix !! :hugs:

Discussion:
<del> { lib, buildGoModule, fetchFromGitHub </del> <ins> { lib, buildGoModule, fetchFromGitHub, fetchpatch </ins> , nixosTests, postgresql, postgresqlTestHook }: buildGoModule rec {

hash = "sha256-2DqEfTXD3W6MxfBb6aHaKH+zpxLc2tHaGuWGQuncySo="; }; <ins> patches = [ # Fix SQLite db lockup (fetchpatch { url = "https://github.com/matrix-org/dendrite/commit/c08c7405dbe9d88c1364f6f1f2466db5045506cc.patch"; hash = "sha256-gTF9jK5Ihfe1v49gPCK68BLeiUZa2Syo+7D9r62iEXQ="; }) ]; </ins> vendorHash = "sha256-dc0zpKh7J+fi2b5GD/0BQ120UXbBvJLUF74RmYMSOMw="; subPackages = [
Change:
Steps to reproduce the behavior: After , uses to determine its default value. That conflicts with the assumption of that no should be set. <!-- 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.
I was able to run the builder in the meantime with this command: the default SSH port in that version is . found it in these are the for reference.

Discussion:
../virtualisation/nixos-containers.nix ../services/x11/desktop-managers/xterm.nix ]; <del> config = { }; </del> <ins> # swraid's default depends on stateVersion config.boot.swraid.enable = false; </ins> options.boot.isContainer = lib.mkOption { default = false; internal = true; }; } ];
Change:
Project description Automatically review and improve your Python code. Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin Analysis Naively installing the package with python works, but at runtime this error is shown most likely because it is a generic linux binary and we need to patchelf it. Is this analysis correct? Pointers Ideally the associated VS Code should be available as well. Related PR is .

Discussion:
meta.license = lib.licenses.lgpl3Only; }; <ins> sourcery.sourcery = callPackage ./sourcery.sourcery { }; </ins> spywhere.guides = buildVscodeMarketplaceExtension { mktplcRef = { name = "guides";

<ins> { lib, stdenv, vscode-utils, autoPatchelfHook, libxcrypt-legacy, }: vscode-utils.buildVscodeMarketplaceExtension { mktplcRef = { name = "sourcery"; publisher = "sourcery"; version = "1.16.0"; hash = "sha256-SHgS2C+ElTJW4v90Wg0QcsSL2FoSz+SxZQpgq2J4JiU="; }; postPatch = '' pushd sourcery_binaries/install rm -r win ${if stdenv.isLinux then "mac" else "linux"} popd ''; nativeBuildInputs = lib.optionals stdenv.isLinux [ autoPatchelfHook ]; buildInputs = [ stdenv.cc.cc.lib libxcrypt-legacy ]; meta = { changelog = "https://sourcery.ai/changelog/"; description = "A VSCode extension for Sourcery, an AI-powered code review and pair programming tool for Python"; downloadPage = "https://marketplace.visualstudio.com/items?itemName=sourcery.sourcery"; homepage = "https://github.com/sourcery-ai/sourcery-vscode"; license = lib.licenses.unfree; maintainers = with lib.maintainers; [ tomasajt ]; platforms = [ "x86_64-linux" "x86_64-darwin" ]; }; } </ins>

<ins> { lib, stdenv, python3Packages, fetchPypi, autoPatchelfHook, libxcrypt-legacy, }: let platformInfos = { "x86_64-linux" = { platform = "manylinux1_x86_64"; hash = "sha256-gr5z8VYkuCqgmcnyA01/Ez6aX9NrKR4MgA0Bc6IHnfs="; }; "x86_64-darwin" = { platform = "macosx_10_9_universal2"; hash = "sha256-5LsxeozPgInUC1QAxDSlr8NIfmRSl5BN+g9/ZYAxiRE="; }; }; platformInfo = platformInfos.${stdenv.system} or (throw "Unsupported platform ${stdenv.system}"); in python3Packages.buildPythonApplication rec { pname = "sourcery"; version = "1.16.0"; format = "wheel"; src = fetchPypi { inherit pname version format; inherit (platformInfo) platform hash; }; nativeBuildInputs = lib.optionals stdenv.isLinux [ autoPatchelfHook ]; buildInputs = [ libxcrypt-legacy ]; meta = { changelog = "https://sourcery.ai/changelog/"; description = "An AI-powered code review and pair programming tool for Python"; downloadPage = "https://pypi.org/project/sourcery/"; homepage = "https://sourcery.ai"; license = lib.licenses.unfree; mainProgram = "sourcery"; maintainers = with lib.maintainers; [ tomasajt ]; platforms = [ "x86_64-linux" "x86_64-darwin" ]; }; } </ins>
Change:
Trying to update a system to the latest "release" () results in the following error: I don't know how to easily reproduce this. At least for me, it seems to happen because the needs to adjusted. So: Try to update a system that (at least) uses ZFS I guess ... No build failure. N/A It looks like this was caused by . I'm not sure if the ZFS module is the only place that needs to be adjusted after this PR has landed. (authored the PR mentioned above) (approved the PR mentioned above) (ZFS maintainers) Please run and paste the result.
For now, I'm not sure, I can reproduce on 23.11pre504982.. It seems like the fix is obvious though.
While I understand how to adjust the two lines in , I don't know how to deal with the other occurrences of in that file.
Usually you can replace "PATH lookup handle where this binary actually is.
I have a potentially fix in
Someone should prove that before the fix, this was broken with a NixOS test ideally and with this fix, this is unbroken.
I suspect it's related to and that that's not covered by any of the existing nixos tests.
And that in turn can't trivially be tested end-to-end because nixos-generate-config doesn't actually support non-legacy zfs mounts... I've written a test and a little prose about the issue:
Maybe we should consider adding them. Using new mounts is rather convenient when the disk needs to be mounted in a live iso.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Ran into the same exact issue over here. Also running on ZFS root. (The discourse link above is mine.) EDIT: Fixed by updating to master. I think I'll be converting to flakes soon, thanks to this
Fix reverted because it broke basically the entire nixos test suite:
I get this with NixOS 23.05.
are you sure it's exactly that? The util-linux split isn't even on 23.05 so that would be very weird.
Yes
That sounds like you're somehow using unstable util-linux for the stable initramfs generation, and it's not surprising that that would break. You can try confirming this by temporarily setting both nixpkgs to point to the same (doesn't even matter if it's unstable or stable).
I have unstable for Alacrity which is an application, I don't see how that would affect initramfs generation.
And I don't see how you'd get a split util-linux from 23.05, since wasn't backported there.
Indeed: And in fact: Which is a different util-linux version number than we see in your error message. Finally, your nix flake metadata says your using , and: So something fishy is going on here. You've got an overlay or override or something that's pulling in a different util-linux from unstable. Either that or there's some other build that's occurring as an unexpected transitive dependency that's building a nixos system using an unstable nixpkgs that doesn't contain the fix. Either way, I feel fairly confident in saying this is some obscure and subtle user error.

Discussion:
copy_bin_and_libs () { [ -f "$out/bin/$(basename $1)" ] && rm "$out/bin/$(basename $1)" <del> cp -pdv $1 $out/bin </del> <ins> cp -pdvH $1 $out/bin </ins> } # Copy BusyBox.
Change:
Steps to reproduce the behavior: on old thinkpad Device: Thinkpad X220 <!-- 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.
greetings ! are you able to test ? an other workaround is to stick to < 6.4 kernel
for now I can't test your commit since I'm newbie and asking you to teach me would take a lot of your time Gonna stick to < 6.4 kernel and try to test commit in free time
appreciate your concerns! from looking at your setup you seem to know fair bit already, and I dont mind spending some time for as long we all learn something useful you should be able to test that PR by changing in your flake to edit: also no rush to test this
Well that was actually easy to test! PR works! I thought I need to use overlays to test it and I have zero experience with them for now.

Discussion:
<del> { stdenv, lib, fetchFromGitHub, kernel, writeScript, coreutils, gnugrep, jq, curl, common-updater-scripts, runtimeShell </del> <ins> { stdenv , lib , fetchFromGitHub , fetchpatch , kernel , writeScript , coreutils , gnugrep , jq , curl , common-updater-scripts , runtimeShell </ins> }: stdenv.mkDerivation rec {

version = "0.43"; src = fetchFromGitHub { <del> owner = "evgeni"; </del> <ins> owner = "linux-thinkpad"; </ins> repo = "tp_smapi"; rev = "tp-smapi/${version}"; sha256 = "1rjb0njckczc2mj05cagvj0lkyvmyk6bw7wkiinv81lw8m90g77g"; <del> name = "tp-smapi-${version}"; </del> }; <ins> patches = [ # update DEFINE_SEMAPHORE usage for linux 6.4+ # https://github.com/linux-thinkpad/tp_smapi/pull/45 (fetchpatch { url = "https://github.com/linux-thinkpad/tp_smapi/commit/0c3398b1acf2a2cabd9cee91dc3fe3d35805fa8b.patch"; hash = "sha256-J/WvijrpHGwFOZMMxnHdNin5eh8vViTcNb4nwsCqsLs="; }) ]; </ins> nativeBuildInputs = kernel.moduleBuildDependencies; hardeningDisable = [ "pic" ];

meta = { description = "IBM ThinkPad hardware functions driver"; <del> homepage = "https://github.com/evgeni/tp_smapi"; </del> <ins> homepage = "https://github.com/linux-thinkpad/tp_smapi"; </ins> license = lib.licenses.gpl2; maintainers = [ ]; # driver is only ment for linux thinkpads i think  bellow platforms should cover it.
Change:
KeePass won't open because there is a missing quotation mark after and one to much after Use unstable Channel. Install KeePass just try to start KeePass via System: 17.09pre104410. (Hummingbird) Nix version: 1.11.8 Nixpkgs version: 17.09pre104410. pkg-name: keepass-2.35
Thanks for reporting! EDIT: I thought that GitHub would immediately close the issue because I pushed a fix but it waits :D
(It actually just takes a minute or so after pushing the commit)
You outran me in cherry-picking ~_^
Hrhr
Just a little question. I'm new on NixOS, so what I've to do to get keepass working again? Just wait and update?
Sorry for the late response -- this should be available in channels now, but generally if you need something ASAP you need to checkout nixpkgs repository at the latest unstable commit and cherry-pick needed patches.

Discussion:
<ins> {stdenv, fetchurl, yacc, flex, pkgconfig, glib, xz}: stdenv.mkDerivation rec { version = "0.15.2"; name = "vala-${version}"; src = fetchurl { url = "mirror://gnome/sources/vala/0.15/${name}.tar.xz"; sha256 = "0g71zq6dpqrw2f40wfzdf18fdw41ymr17laqniy2kr622hkxdi8w"; }; buildNativeInputs = [ yacc flex pkgconfig xz ]; buildInputs = [ glib ]; meta = { description = "Compiler for the GObject type system"; homepage = "http://live.gnome.org/Vala"; license = "free-copyleft"; platforms = stdenv.lib.platforms.all; maintainers = [ stdenv.lib.maintainers.antono ]; }; } </ins>

<ins> {stdenv, fetchurl, yacc, flex, pkgconfig, glib, xz}: stdenv.mkDerivation rec { version = "0.16.1"; name = "vala-${version}"; src = fetchurl { url = "mirror://gnome/sources/vala/0.16/${name}.tar.xz"; sha256 = "1n708n9ixyy9qrzyv1wf4ybvcclx43ib9ki028wwpvkz6kv8zqlb"; }; buildNativeInputs = [ yacc flex pkgconfig xz ]; buildInputs = [ glib ]; meta = { description = "Compiler for the GObject type system"; homepage = "http://live.gnome.org/Vala"; license = "free-copyleft"; platforms = stdenv.lib.platforms.all; maintainers = [ stdenv.lib.maintainers.antono ]; }; } </ins>

{stdenv, fetchurl, yacc, flex, pkgconfig, glib, xz}: stdenv.mkDerivation rec { <del> name = "vala-0.14.2"; </del> <ins> version = "0.17.2"; name = "vala-${version}"; </ins> src = fetchurl { <del> url = mirror://gnome/sources/vala/0.14/vala-0.14.2.tar.xz; sha256 = "1l5kllw9vpwv24lzv9fp64l3sad46wpxgvsgryrwlrjg91w6jzl0"; </del> <ins> url = "mirror://gnome/sources/vala/0.17/${name}.tar.xz"; sha256 = "09i2s0dwmrk147ind2dx7nq845g12fp6fsjqrphhrr0dbi0zzgh3"; </ins> }; buildNativeInputs = [ yacc flex pkgconfig xz ];

meta = { description = "Compiler for the GObject type system"; homepage = "http://live.gnome.org/Vala"; <ins> license = "free-copyleft"; platforms = stdenv.lib.platforms.all; maintainers = [ stdenv.lib.maintainers.antono ]; </ins> }; }

urweb = callPackage ../development/compilers/urweb { }; <del> vala = callPackage ../development/compilers/vala { }; </del> <ins> vala = vala17; vala15 = callPackage ../development/compilers/vala/15.2.nix { }; vala16 = callPackage ../development/compilers/vala/16.1.nix { }; vala17 = callPackage ../development/compilers/vala/default.nix { }; </ins> visualcpp = callPackage ../development/compilers/visual-c++ { };
Change:
The links in has been broken. Them link from , but in fact should be Steps to reproduce the behavior: in your NixOS configuration. your NixOS the , you will be told an error when opening the links in ! <!-- 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.

Discussion:
environment.systemPackages = [ pkgs.udisks2 ]; <del> environment.etc = (mapAttrs' (name: value: nameValuePair "udisks2/${name}" { source = value; } ) configFiles) // { # We need to make sure /etc/libblockdev/conf.d is populated to avoid </del> <ins> environment.etc = (mapAttrs' (name: value: nameValuePair "udisks2/${name}" { source = value; } ) configFiles) // ( let libblockdev = pkgs.udisks2.libblockdev; majorVer = versions.major libblockdev.version; in { # We need to make sure /etc/libblockdev/@major_ver@/conf.d is populated to avoid </ins> # warnings <del> "libblockdev/conf.d/00-default.cfg".source = "${pkgs.libblockdev}/etc/libblockdev/conf.d/00-default.cfg"; "libblockdev/conf.d/10-lvm-dbus.cfg".source = "${pkgs.libblockdev}/etc/libblockdev/conf.d/10-lvm-dbus.cfg"; }; </del> <ins> "libblockdev/${majorVer}/conf.d/00-default.cfg".source = "${libblockdev}/etc/libblockdev/${majorVer}/conf.d/00-default.cfg"; "libblockdev/${majorVer}/conf.d/10-lvm-dbus.cfg".source = "${libblockdev}/etc/libblockdev/${majorVer}/conf.d/10-lvm-dbus.cfg"; }); </ins> security.polkit.enable = true;

doCheck = true; <del> passthru.tests.vm = nixosTests.udisks2; </del> <ins> passthru = { inherit libblockdev; tests.vm = nixosTests.udisks2; }; </ins> meta = with lib; { description = "A daemon, tools and libraries to access and manipulate disks, storage devices and technologies";
Change:
Steps to reproduce the behavior: to install ansible on OSX 13.4 (via fleek) I'm not using nix vanilla but fleek Please run and paste the result.
Just hit this one too, on aarch64-darwin.
I have this issue on x86_64-darwin as well, so it's not architecture specific.
I remember you investigated this and had a fix in mind. Just putting this issue on your radar.
I do. The multiprocessing tests don’t work on Darwin. I was going to open a PR after my clang 16 test flake finished building, but I’ll cherry-pick and open one now since the issue is affecting users.

Discussion:
"maxminddb" ]; <ins> # The multiprocessing tests fail on Darwin because multiprocessing uses spawn instead of fork, # resulting in an exception when it can’t pickle the `lookup` local function. disabledTests = lib.optionals stdenv.isDarwin [ "multiprocessing" ]; </ins> meta = with lib; { description = "Reader for the MaxMind DB format"; homepage = "https://github.com/maxmind/MaxMind-DB-Reader-python";
Change:
Package name: session-desktop Latest released version: 1.11.0 <!-- Search your package here: --- Current version on the unstable channel: 1.10.8 Current version on the stable/release channel: 1.10.8 <!-- 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.

Discussion:
}: let <del> version = "1.10.8"; </del> <ins> version = "1.11.0"; </ins> pname = "session-desktop"; src = fetchurl { url = "https://github.com/oxen-io/session-desktop/releases/download/v${version}/session-desktop-linux-x86_64-${version}.AppImage"; <del> sha256 = "sha256-r/MQlZ3dmQmQZ/FCYIIF2sh9+VXwG97PFfTIXIQijx8="; </del> <ins> sha256 = "sha256-QartWtp5/OtJqQq5GXRoIQ/ytK9/YCW1ixXTUrnGwqw="; </ins> }; appimage = appimageTools.wrapType2 { inherit version pname src;
Change:
There is a issue when trying to add this ( ) to the boot.extraModulePackages list. As noted by clever in irc "all out-of-tree modules should be in packagesFor, which lets you just boot.extraModulePackages = [ ];" Steps to reproduce the behavior: boot.extraModulePackages = [ ( { kernel = ; }) ]; is what is needed but boot.extraModulePackages = [ ]; is the expected. boot.extraModulePackages = [ ]; in the hardware- This is needed to get the gasket kernel module so that /dev/apex_X devices show up under /dev/ Please run and paste the result.
I think is supposed to solve this? I just don't know how to get it unstuck.
I used this for a work-around:
There's a new patch that allows building with 6.4 kernels as well.
A quick workaround to get this to build on . This includes the kernel override discussed above, and uses a later version of the upstream that includes support for kernels = 6.4. Upstream does not seem to add version numbers very frequently, so this uses the first 6 charaters of the git revision as version.

Discussion:
stdenv.mkDerivation rec { pname = "gasket"; <del> version = "1.0-18"; </del> <ins> version = "1.0-18-unstable-2023-09-05"; </ins> src = fetchFromGitHub { owner = "google"; repo = "gasket-driver"; <del> rev = "97aeba584efd18983850c36dcf7384b0185284b3"; sha256 = "pJwrrI7jVKFts4+bl2xmPIAD01VKFta2SRuElerQnTo="; </del> <ins> rev = "09385d485812088e04a98a6e1227bf92663e0b59"; sha256 = "fcnqCBh04e+w8g079JyuyY2RPu34M+/X+Q8ObE+42i4="; </ins> }; makeFlags = [
Change:
after suspend the network-manager applet in plasma5/kde disappears suspend resume search for nm applet log out log in its back
Does this still happen on ? I cannot reproduce it.
i am no longer using nixos

Discussion:
wireless.enable = lib.mkDefault false; }; <del> powerManagement.resumeCommands = '' ${config.systemd.package}/bin/systemctl restart network-manager ''; </del> security.polkit.extraConfig = polkitConf; services.dbus.packages = cfg.packages;
Change:
Nix fails to build on nixpkgs master. Steps to reproduce the behavior: unstable channel -channel --update works: fails: failure: Both invocations should succeed as they are isomorphic, i.e. has an unused let binding that causes to fail. Looks like this PR may have introduced the assert that causes the problem , After some investigation a colleague pointed out that the issue may have to do with the instability of attrset comparison due to laziness in nix, comparison happens here and looks like invocation in somehow cause a different evaluation order of attrset attribute comparison: if isStatic is compared first we don't see the assert If extensions compares first we stumble on the assert and fail. who the assert that fails nix package maintainers Please run and paste the result.
With something like we can deterministically crash the eval:
Same issue in
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
This was my fault. The fix is: Unfortunately we can't provide useful error messages when people use sub-attributes of , because it is expected that you can compare two attrsets using , which will force the . We should probably move anything fallible (like ) out of these attrsets, so we can provide useful error messages instead of just returning .

Discussion:
# is why we use the more obscure "bfd" and not "binutils" for this # choice. else                                     "bfd"; <del> extensions = rec { sharedLibrary = assert final.hasSharedLibraries; /**/ if final.isDarwin  then ".dylib" </del> <ins> extensions = lib.optionalAttrs final.hasSharedLibraries { sharedLibrary = if      final.isDarwin  then ".dylib" </ins> else if final.isWindows then ".dll" else                         ".so"; <ins> } // { </ins> staticLibrary = /**/ if final.isWindows then ".lib" else                         ".a"; library = <del> /**/ if final.isStatic then staticLibrary else                        sharedLibrary; </del> <ins> /**/ if final.isStatic then final.extensions.staticLibrary else                        final.extensions.sharedLibrary; </ins> executable = /**/ if final.isWindows then ".exe" else                         "";
Change:
Package name: tenacity Latest released version: 1.3.1 <!-- Search your package here: --- Current version on the unstable channel: 1.3-beta2 Current version on the stable/release channel: 1.3-beta2 So, wanted to use tenacity because i'm not letting my grudge against muse go, sorry, when i noticed something odd: the version in nixpkgs is older than the latest release. appears there's no mechanism to alert maintainers of updates for this automatically so here's an issue i guess <!-- 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.
oh hey yep, that's me! thanks for the heads up, I'll get on that
(and I feel similarly about the whole audacity mess, it's why I packaged tenacity. I think this will be the first time there's been a proper stable tenacity release in nixpkgs, I'm looking forward to it.)

Discussion:
stdenv.mkDerivation rec { pname = "tenacity"; <del> version = "1.3-beta2"; </del> <ins> version = "1.3.1"; </ins> src = fetchFromGitea { domain = "codeberg.org"; owner = "tenacityteam"; repo = pname; rev = "v${version}"; <del> sha256 = "sha256-9gWoqFa87neIvRnezWI3RyCAOU4wKEHPn/Hgj3/fol0="; </del> <ins> sha256 = "sha256-wesnay+UQiPSDaRuSo86MgHdElN4s0rPIvokZhKM7GI="; </ins> }; postPatch = ''

''; postFixup = '' <del> rm $out/audacity </del> <ins> rm $out/tenacity </ins> wrapProgram "$out/bin/tenacity"  --suffix AUDACITY_PATH : "$out/share/tenacity"  --suffix AUDACITY_MODULES_PATH : "$out/lib/tenacity/modules"