jiebi/CodeConvo huggingface dataset:
Code change:
the ruby gem tzinfo exists in two different versions/branches which are both maintained. the branch does not contain the file referenced by nixpkgs, only 1.x does. Ref: Extract from pkgs/development/ruby-modules/gem- I fixed it by overwriting tzinfo (again!) but this is not a good solution :/ cc System: (NixOS: , Ubuntu/Fedora: , ...) Nix version: (run ) Nixpkgs version: (run )
Hmm. I don't remember by heart, is available? If yes we could switch based on the version. Pseudo code:

Related discussion:
text: {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 ];
Code change:
the ruby gem tzinfo exists in two different versions/branches which are both maintained. the branch does not contain the file referenced by nixpkgs, only 1.x does. Ref: Extract from pkgs/development/ruby-modules/gem- I fixed it by overwriting tzinfo (again!) but this is not a good solution :/ cc System: (NixOS: , Ubuntu/Fedora: , ...) Nix version: (run ) Nixpkgs version: (run )
Hmm. I don't remember by heart, is available? If yes we could switch based on the version. Pseudo code:

Related discussion:
text: 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> }; }
Code change:
the ruby gem tzinfo exists in two different versions/branches which are both maintained. the branch does not contain the file referenced by nixpkgs, only 1.x does. Ref: Extract from pkgs/development/ruby-modules/gem- I fixed it by overwriting tzinfo (again!) but this is not a good solution :/ cc System: (NixOS: , Ubuntu/Fedora: , ...) Nix version: (run ) Nixpkgs version: (run )
Hmm. I don't remember by heart, is available? If yes we could switch based on the version. Pseudo code:

Related discussion:
text: 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++ { };
Code change:
webUISupport is needed for the command. However, enabling this flag fails the tree-sitter build. Steps to reproduce the behavior: to your favorite checkout of nixpkgs A successful build. I'll give you a section of the build log instead: Please run and paste the result.
I still get this error with tree-sitter 0.20.9 in a Nix flake. Did setting the emcc cache outside the nix store fix the build for you?
If I try to reproduce it, I get this error: Which looks similar, but I think is a distinct issue. I do not think this is related to the emcc cache. I think it's best if you open a new issue for this. The emcc cache is not set in the Nix store btw, it is set in a nix build directory, wherever that may be. You can generally not set the emcc cache somewhere outside of the nix sandbox.
Sounds good. Thanks for the clarification. Wasn't sure if there was a setting I was missing
I've got a PR out (see above) to fix this new issue.
Awesome. Thank you

Related discussion:
text: # minifying the JavaScript; passing it allows us to side-step more Node # JS dependencies for installation. preBuild = lib.optionalString webUISupport '' <ins> mkdir -p .emscriptencache export EM_CACHE=$(pwd)/.emscriptencache </ins> bash ./script/build-wasm --debug '';
Code change:
Project description python docstring generator <!-- Describe the project a little: --Metadata homepage URL: source URL: license: bsd platforms: unix, linux, darwin, ...

Related discussion:
text: <ins> { lib , python3 , fetchFromGitHub }: python3.pkgs.buildPythonApplication rec { pname = "doq"; version = "0.9.1"; format = "setuptools"; src = fetchFromGitHub { owner = "heavenshell"; repo = "py-doq"; rev = "refs/tags/${version}"; hash = "sha256-6ff7R/2Jo4jYm1hA70yopjklpKIMWlj7DH9eKxOlfgU="; }; propagatedBuildInputs = with python3.pkgs; [ jinja2 parso toml ]; nativeCheckInputs = with python3.pkgs; [ parameterized unittestCheckHook ]; pythonImportsCheck = [ "doq" ]; meta = with lib; { description = "Docstring generator for Python"; homepage = "https://github.com/heavenshell/py-doq"; changelog = "https://github.com/heavenshell/py-doq/releases/tag/${src.rev}"; license = licenses.bsd3; maintainers = with maintainers; [ natsukium ]; }; } </ins>
Code change:
Project description python docstring generator <!-- Describe the project a little: --Metadata homepage URL: source URL: license: bsd platforms: unix, linux, darwin, ...

Related discussion:
text: dbus-test-runner = callPackage ../development/tools/dbus-test-runner { }; <ins> doq = callPackage ../development/tools/misc/doq { }; </ins> phpunit = callPackage ../development/tools/misc/phpunit { }; teller = callPackage ../development/tools/teller { };
Code change:
Project description Virter is a command line tool for simple creation and cloning of virtual machines based on libvirt Metadata homepage URL: source URL: Blogs: , license: Apache v2 platforms: Linux only written in: go Thanks a ton!

Related discussion:
text: <ins> { lib , buildGoModule , fetchFromGitHub }: buildGoModule rec { pname = "virter"; version = "0.25.0"; src = fetchFromGitHub { owner = "LINBIT"; repo = "virter"; rev = "v${version}"; hash = "sha256-NIZBaPYFFH3MG2M7rF39TW8sLVR44SA37ZU3gOPwAFU="; }; vendorHash = "sha256-cVOxRrsDdtlDSJ3WRDNk8nqt7ztz4GSRIf6FDDBxvPc="; ldflags = [ "-s" "-w" "-X github.com/LINBIT/virter/cmd.version=${version}" "-X github.com/LINBIT/virter/cmd.builddate=builtByNix" "-X github.com/LINBIT/virter/cmd.githash=builtByNix" ]; # requires network access doCheck = false; meta = { description = "A command line tool for simple creation and cloning of virtual machines based on libvirt"; homepage = "https://github.com/LINBIT/virter"; license = lib.licenses.asl20; maintainers = with lib.maintainers; [ dit7ya ]; }; } </ins>
Code change:
Project description Virter is a command line tool for simple creation and cloning of virtual machines based on libvirt Metadata homepage URL: source URL: Blogs: , license: Apache v2 platforms: Linux only written in: go Thanks a ton!

Related discussion:
text: viw = callPackage ../applications/editors/viw { }; <ins> virter = callPackage ../applications/virtualization/virter { }; </ins> virt-viewer = callPackage ../applications/virtualization/virt-viewer { }; virt-top = callPackage ../applications/virtualization/virt-top { };
Code change:
When attempting to configure the integration I get an error in Home Assistant Steps to reproduce the behavior: to to configure integration from Home Assistant UI Able to configure <!-- 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.
The package does not eval on master right now, because of a dependency being flagged as disabled for python 3.11. Though I'd be surprised if that is your issue. nix-replhome- error: … while evaluating the attribute 'drvPath' at 221| in commonAttrs // { 222| drvPath = assert condition; drv.drvPath; | ^ 223| outPath = assert condition; drv.outPath; … while evaluating the attribute 'drvPath' at 221| in commonAttrs // { 222| drvPath = assert condition; drv.drvPath; | ^ 223| outPath = assert condition; drv.outPath; (stack trace truncated; use '--show-trace' to show the full trace) error: cherrypy-18.8.0 not supported for interpreter python3.11
Regardless, at least makes evaluate.

Related discussion:
text: "tests/test_cookies.py" ]; <ins> # cherrypy does not support Python 3.11 doCheck = pythonOlder "3.11"; </ins> meta = { changelog = "https://github.com/jaraco/jaraco.net/blob/${src.rev}/CHANGES.rst"; description = "Networking tools by jaraco";
Code change:
The Haskell Hackage database allows distros to report which packages they ship, and include a link. Right now, it seems that nixpkgs reports all haskell packags, including broken ones. This makes for a bad user experience – I might see on hackage that nixos comes with a certain package, and then happily go ahead trying to use it, only later to get the dreaded error message. Same actually for repology, reporting packages as available that we know do not build is not great.
We intend to support all package. We just need haskell maintainer
Oh, absolutely! Maybe I shouldn't say “supported” but “available”.
No, we don't. We only intend to support packages which have value to our users. Hackage is append only and contains a lot of dead or niche packages.
I agree this should have been fixed long ago.

Related discussion:
text: let version = pkg.version or ""; in <del> lib.optionalString (isPvpVersion version) </del> <ins> lib.optionalString (isPvpVersion version && (pkg.meta.hydraPlatforms or null) != lib.platforms.none) </ins> ''"${name}","${version}","http://hydra.nixos.org/job/nixpkgs/trunk/haskellPackages.${name}.x86_64-linux"''; all-haskellPackages = builtins.toFile "all-haskellPackages" (lib.concatStringsSep "n" (lib.filter (x: x != "") (lib.mapAttrsToList pkgLine haskellPackages))); in runCommand "hackage-package-list" { } # This command will make a join between all packages on hackage and haskellPackages.*. <ins> # It ignores packages marked as broken (according to hydraPlatforms) </ins> # It creates a valid csv file which can be uploaded to hackage.haskell.org. # The call is wrapped in echo $(...) to trim trailing newline, which hackage requires. ''
Code change:
VSCode/VSCodium's desktop icon (specified in the file) is set to . On the icon theme (the default dark icon theme that comes with Budgie desktop on NixOS), this makes it look like a generic text editor, and not the respective application. The issue appears to arise from how both apps use the same desktop files that were inherited from :   NixOS w/ Budgie desktop Icon theme to Qogir/Qogir-dark VSCodium/VSCode app list VSCode should use the icon VSCodium should use the icon ! My NixOS install is running in a VMWare VM.

Related discussion:
text: comment = "Code Editing. Redefined."; genericName = "Text Editor"; exec = "${executableName} %F"; <del> icon = "code"; </del> <ins> icon = "vs${executableName}"; </ins> startupNotify = true; startupWMClass = shortName; categories = [ "Utility" "TextEditor" "Development" "IDE" ];
Code change:
VSCode/VSCodium's desktop icon (specified in the file) is set to . On the icon theme (the default dark icon theme that comes with Budgie desktop on NixOS), this makes it look like a generic text editor, and not the respective application. The issue appears to arise from how both apps use the same desktop files that were inherited from :   NixOS w/ Budgie desktop Icon theme to Qogir/Qogir-dark VSCodium/VSCode app list VSCode should use the icon VSCodium should use the icon ! My NixOS install is running in a VMWare VM.

Related discussion:
text: actions.new-empty-window = { name = "New Empty Window"; exec = "${executableName} --new-window %F"; <del> icon = "code"; </del> <ins> icon = "vs${executableName}"; </ins> }; };
Code change:
VSCode/VSCodium's desktop icon (specified in the file) is set to . On the icon theme (the default dark icon theme that comes with Budgie desktop on NixOS), this makes it look like a generic text editor, and not the respective application. The issue appears to arise from how both apps use the same desktop files that were inherited from :   NixOS w/ Budgie desktop Icon theme to Qogir/Qogir-dark VSCodium/VSCode app list VSCode should use the icon VSCodium should use the icon ! My NixOS install is running in a VMWare VM.

Related discussion:
text: comment = "Code Editing. Redefined."; genericName = "Text Editor"; exec = executableName + " --open-url %U"; <del> icon = "code"; </del> <ins> icon = "vs${executableName}"; </ins> startupNotify = true; categories = [ "Utility" "TextEditor" "Development" "IDE" ]; mimeTypes = [ "x-scheme-handler/vscode" ];
Code change:
VSCode/VSCodium's desktop icon (specified in the file) is set to . On the icon theme (the default dark icon theme that comes with Budgie desktop on NixOS), this makes it look like a generic text editor, and not the respective application. The issue appears to arise from how both apps use the same desktop files that were inherited from :   NixOS w/ Budgie desktop Icon theme to Qogir/Qogir-dark VSCodium/VSCode app list VSCode should use the icon VSCodium should use the icon ! My NixOS install is running in a VMWare VM.

Related discussion:
text: ln -s "$desktopItem/share/applications/${executableName}.desktop" "$out/share/applications/${executableName}.desktop" ln -s "$urlHandlerDesktopItem/share/applications/${executableName}-url-handler.desktop" "$out/share/applications/${executableName}-url-handler.desktop" <ins> # These are named vscode.png, vscode-insiders.png, etc to match the name in upstream *.deb packages. </ins> mkdir -p "$out/share/pixmaps" <del> cp "$out/lib/vscode/resources/app/resources/linux/code.png" "$out/share/pixmaps/code.png" </del> <ins> cp "$out/lib/vscode/resources/app/resources/linux/code.png" "$out/share/pixmaps/vs${executableName}.png" </ins> # Override the previously determined VSCODE_PATH with the one we know to be correct sed -i "/ELECTRON=/iVSCODE_PATH='$out/lib/vscode'" "$out/bin/${executableName}"
Code change:
VSCode/VSCodium's desktop icon (specified in the file) is set to . On the icon theme (the default dark icon theme that comes with Budgie desktop on NixOS), this makes it look like a generic text editor, and not the respective application. The issue appears to arise from how both apps use the same desktop files that were inherited from :   NixOS w/ Budgie desktop Icon theme to Qogir/Qogir-dark VSCodium/VSCode app list VSCode should use the icon VSCodium should use the icon ! My NixOS install is running in a VMWare VM.

Related discussion:
text: mkdir -p "$out/share/applications" mkdir -p "$out/share/pixmaps" <del> ln -sT "${vscode}/share/pixmaps/code.png" "$out/share/pixmaps/code.png" </del> <ins> ln -sT "${vscode}/share/pixmaps/vs${executableName}.png" "$out/share/pixmaps/vs${executableName}.png" </ins> ln -sT "${vscode}/share/applications/${executableName}.desktop" "$out/share/applications/${executableName}.desktop" ln -sT "${vscode}/share/applications/${executableName}-url-handler.desktop" "$out/share/applications/${executableName}-url-handler.desktop" makeWrapper "${vscode}/bin/${executableName}" "$out/bin/${executableName}" ${extensionsFlag}
Code change:
I use the following listing in to install a custom keyboard layout: This refers to files in the following structure: This worked until recently (last updated a few months ago), but now fails to build: <details<summaryFull trace</summary</detailsCommenting out the line causes the same error but for . Adding in plausible files in the suggested places also doesn't fix the issue. Steps to reproduce the behavior: up the configuration as above. . The system successfully builds, and I have access to the custom layout. <!-- 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.
Sorry, I forgot to notify maintainers, but I think it's just
This breakage happened with with the update of as they have switched to the meson build system.
Thanks, that's really helpful! I suppose I'll revert to before that merge for now (though I'm finding it hard to find the list of good commit hashes). Do you know any other workarounds?
You can use . that does not have those changes. For a list you can look at in the "Input changes" column. That is a log of the "nixos-unstable" branch, for which the binary cache has been filled after a few tests have been run.
The script that patches the makefile to include the extra layouts need to be updated.
Can you test if your layouts work correctly with ? I a test for a basic file but I haven't tried other types.
Works fine for me but I also only use symbols
Fix merged, you can track the progress to nixos-unstable .

Related discussion:
text: mkKeyboardTest = layout: { extraConfig ? {}, tests }: with pkgs.lib; makeTest { name = "keymap-${layout}"; <del> machine.console.keyMap = mkOverride 900 layout; machine.services.xserver.desktopManager.xterm.enable = false; machine.services.xserver.layout = mkOverride 900 layout; machine.imports = [ ./common/x11.nix extraConfig ]; </del> <ins> nodes.machine.console.keyMap = mkOverride 900 layout; nodes.machine.services.xserver.desktopManager.xterm.enable = false; nodes.machine.services.xserver.layout = mkOverride 900 layout; nodes.machine.imports = [ ./common/x11.nix extraConfig ]; </ins> testScript = '' import json
Code change:
I use the following listing in to install a custom keyboard layout: This refers to files in the following structure: This worked until recently (last updated a few months ago), but now fails to build: <details<summaryFull trace</summary</detailsCommenting out the line causes the same error but for . Adding in plausible files in the suggested places also doesn't fix the issue. Steps to reproduce the behavior: up the configuration as above. . The system successfully builds, and I have access to the custom layout. <!-- 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.
Sorry, I forgot to notify maintainers, but I think it's just
This breakage happened with with the update of as they have switched to the meson build system.
Thanks, that's really helpful! I suppose I'll revert to before that merge for now (though I'm finding it hard to find the list of good commit hashes). Do you know any other workarounds?
You can use . that does not have those changes. For a list you can look at in the "Input changes" column. That is a log of the "nixos-unstable" branch, for which the binary cache has been filled after a few tests have been run.
The script that patches the makefile to include the extra layouts need to be updated.
Can you test if your layouts work correctly with ? I a test for a basic file but I haven't tried other types.
Works fine for me but I also only use symbols
Fix merged, you can track the progress to nixos-unstable .

Related discussion:
text: extraConfig.console.keyMap = "de"; extraConfig.services.xserver.layout = "de"; }; <ins> custom = { tests = { us.qwerty = [ "a" "b" "g" "d" "z" "shift-2" "shift-3" ]; us.expect = [ "a" "b" "g" "d" "z" "@" "#" ]; greek.qwerty = map (x: "alt_r-${x}") [ "a" "b" "g" "d" "z" ]; greek.expect = [ "α" "β" "γ" "δ" "ζ" ]; }; extraConfig.console.useXkbConfig = true; extraConfig.services.xserver.layout = "us-greek"; extraConfig.services.xserver.extraLayouts.us-greek = { description = "US layout with alt-gr greek"; languages   = [ "eng" ]; symbolsFile = pkgs.writeText "us-greek" '' xkb_symbols "us-greek" { include "us(basic)" include "level3(ralt_switch)" key <LatA> { [ a, A, Greek_alpha ] }; key <LatB> { [ b, B, Greek_beta  ] }; key <LatG> { [ g, G, Greek_gamma ] }; key <LatD> { [ d, D, Greek_delta ] }; key <LatZ> { [ z, Z, Greek_zeta  ] }; }; ''; }; }; </ins> }
Code change:
I use the following listing in to install a custom keyboard layout: This refers to files in the following structure: This worked until recently (last updated a few months ago), but now fails to build: <details<summaryFull trace</summary</detailsCommenting out the line causes the same error but for . Adding in plausible files in the suggested places also doesn't fix the issue. Steps to reproduce the behavior: up the configuration as above. . The system successfully builds, and I have access to the custom layout. <!-- 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.
Sorry, I forgot to notify maintainers, but I think it's just
This breakage happened with with the update of as they have switched to the meson build system.
Thanks, that's really helpful! I suppose I'll revert to before that merge for now (though I'm finding it hard to find the list of good commit hashes). Do you know any other workarounds?
You can use . that does not have those changes. For a list you can look at in the "Input changes" column. That is a log of the "nixos-unstable" branch, for which the binary cache has been filled after a few tests have been run.
The script that patches the makefile to include the extra layouts need to be updated.
Can you test if your layouts work correctly with ? I a test for a basic file but I haven't tried other types.
Works fine for me but I also only use symbols
Fix merged, you can track the progress to nixos-unstable .

Related discussion:
text: ${optionalString (symbolsFile  != null) "cp '${symbolsFile}'  'symbols/${name}'"} ${optionalString (typesFile    != null) "cp '${typesFile}'    'types/${name}'"} <del> # patch makefiles for type in compat geometry keycodes symbols types; do if ! test -f "$type/${name}"; then continue fi test "$type" = geometry && type_name=geom || type_name=$type ${ed}/bin/ed -v $type/Makefile.am <<EOF /''${type_name}_DATA = a ${name}  . w EOF ${ed}/bin/ed -v $type/Makefile.in <<EOF /''${type_name}_DATA = a ${name}  . w EOF done </del> # add model description ${ed}/bin/ed -v rules/base.xml <<EOF /</modelList>
Code change:
Steps to reproduce the behavior: X Add any other context about the problem here. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result.

Related discussion:
text: python3.pkgs.buildPythonApplication rec { pname = "dvc"; <del> version = "3.5.0"; </del> <ins> version = "3.5.1"; </ins> format = "pyproject"; src = fetchFromGitHub { owner = "iterative"; repo = pname; rev = "refs/tags/${version}"; <del> hash = "sha256-AQE8KQ5j/EgN1P2HFghWXgQJbBc+KYu8kwNeV0Tktho="; </del> <ins> hash = "sha256-1kVc7+36rvIpoSinpyxMMs1/nhZrwv1pPWJsruFd1N8="; </ins> }; pythonRelaxDeps = [
Code change:
Project description EteSync is a "secure, end-to-end encrypted, and privacy respecting sync for your contacts, calendars, tasks and notes." Since GSoC 2020 KDE supports it. automatically detects if it is installed and builds the appropriate modules. Metadata homepage URL: ("build from source" link points to a site that is gone) build instructions: source URL: license: BSD-3-Clause platforms: unix, linux, darwin, ...

Related discussion:
text: <ins> { rustPlatform , fetchFromGitHub , pkg-config , openssl , lib , stdenv , testers , libetebase }: rustPlatform.buildRustPackage rec { pname = "libetebase"; version = "0.5.6"; src = fetchFromGitHub { owner = "etesync"; repo = "libetebase"; rev = "v${version}"; hash = "sha256-cXuOKfyMdk+YzDi0G8i44dyBRf4Ez5+AlCKG43BTSSU="; }; cargoHash = "sha256-GUNj5GrY04CXnej3WDKZmW4EeJhoCl2blHSDfEkQKtE="; nativeBuildInputs = [ pkg-config ]; buildInputs = [ openssl ]; postInstall = '' install -d $out/lib/pkgconfig sed s#@prefix@#$out#g etebase.pc.in > $out/lib/pkgconfig/etebase.pc install -Dm644 EtebaseConfig.cmake -t $out/lib/cmake/Etebase install -Dm644 target/etebase.h -t $out/include/etebase ln -s $out/lib/libetebase.so $out/lib/libetebase.so.0 ''; passthru.tests.pkgs-config = testers.testMetaPkgConfig libetebase; meta = with lib; { description = "A C library for Etebase"; homepage = "https://www.etebase.com/"; license = licenses.bsd3; broken = stdenv.isDarwin; maintainers = with maintainers; [ laalsaas ]; pkgConfigModules = [ "etebase" ]; }; } </ins>